Project

General

Profile

Actions
Copy link

Feature #1496

closed

no rewrite after cookie cond (config merging)

Added by Anonymous over 16 years ago. Updated almost 8 years ago.

Status:
Wontfix
Priority:
Normal
Category:
core
Target version:
-
ASK QUESTIONS IN Forums:

Description

When the following cookie condition is true the First Rewrite didn't work anymore.


url.rewrite-once = (
    "^/test" => "/ftc.php" 
)

$HTTP["cookie"] !~ "foo=bar" {
    url.rewrite-once = (
        "^/foo" => "/bar.php" 
    )
}

I have this Problem in the 1.4.18 and the lighttpd-1.5.0-r1992.

Actions
Copy link
 #1

Updated by gstrauss almost 8 years ago

  • Tracker changed from Bug to Feature
  • Subject changed from no rewrite after cookie cond. to no rewrite after cookie cond (config merging)
  • Description updated (diff)
  • Assignee deleted (jan)
  • Priority changed from High to Normal
  • Target version changed from 1.5.0 to 1.4.x

This is probably an unfortunate (and not very user-friendly) limitation in lighttpd config merging.
Please find further explanation at https://redmine.lighttpd.net/boards/2/topics/6541

Actions
Copy link
 #2

Updated by gstrauss almost 8 years ago

  • Status changed from New to Wontfix

This is probably an unfortunate (and not very user-friendly) limitation in lighttpd config merging.
Please find further explanation at https://redmine.lighttpd.net/boards/2/topics/6541

Marking Wontfix only because changing this behavior might break (someone else's) existing configs.

I realize that duplicating rule is not ideal, but as a workaround, you can repeat the rewrite rules in each block where you assign url.rewrite-once = (...)

Actions
Copy link
 #3

Updated by stbuehler almost 8 years ago

  • Target version deleted (1.4.x)
Actions
Copy link

Also available in: Atom