Bug #1827
closed400 Response on any URL that countains a space character (ASCII 20)
Description
Any url that contains a space (encoded as %20, or ASCII 20) fails with a 400 error. This seems to be linked to (or a duplicate of) http://redmine.lighttpd.net/issues/show/1822
I'd appreciate if someone could confirm this.
Updated by catmando about 16 years ago
Sorry in my rush i forgot to mention that this is in 1.4.20
Updated by Jine about 16 years ago
Updated by peto about 16 years ago
There's no way this bug exists.
(And, er, ASCII 32, not 20.)
Updated by catmando about 16 years ago
@Jine:
http://wwpde00.securesites.net/testbed/rewrite%20test
Compare to:
http://wwpde00.securesites.net:8001/testbed/rewrite%20test
I'm sorry to have been unclear again, but it seems that this is a rewrite problem. Static content does indeed seem to serve just fine, but the whole reason I love lighty is because it makes my CMS sites go super fast! I was in a rush as I had to catch a train.
The particular rewrite rule where I think the problem is looks like this:
$HTTP["host"] == "wwpde00.securesites.net"{
url.rewrite-once = ( "^/(.*)$" => "/VirtualHostBase/http/wwpde00.securesites.net:80//VirtualHostRoot/$1")
proxy.balance = "hash"
proxy.server = ( "/VirtualHostBase" => ( ( "host" => "127.0.0.1", "port" => 8001 ) ) )
}
@peto:
The bug does exist, it's just in the rewrite module. And ASCII 32 decimal == ASCII 20 hex (i.e. what's actually used on the web).
Also available in: Atom