Project

General

Profile

Bug #1631

inconsistent behaviour when using querystring match in combination with url.rewrite

Added by Anonymous over 11 years ago. Updated almost 11 years ago.

Status:
Invalid
Priority:
Normal
Assignee:
-
Category:
core
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Missing in 1.5.x:

Description

I use the following config:

url.rewrite = (".*" => ".pl?foo=bar")
$HTTPquerystring =~ "foo" {
url.redirect = ( "(.*)" => "http://www.google.nl" )
}

Now if I call curl like this
% curl --verbose 'http://www.foo.nl/'
lighttpd correctly redirects to google the first time but every other time it will NOT redirect! So it seems it matches the first time on the querystring AFTER url.rewrite and every other time it matches on the querystring BEFORE url.rewrite.

Furthermore, it seems that matching on $HTTPurl always takes place after url.rewrite and matching on $HTTPquerystring takes place BEFORE url.rewrite (well, except for the first time). I wonder if this is consistent with the specs and/or what people expect?

-- aiso

History

#1

Updated by Anonymous over 11 years ago

With first time I mean immediately after restarting lighttpd

-- aiso

#2

Updated by stbuehler over 11 years ago

  • Status changed from New to Fixed
  • Resolution set to invalid

Already fixed in 1.4.19.

#3

Updated by stbuehler almost 11 years ago

  • Status changed from Fixed to Invalid

Also available in: Atom