Bug #1827

400 Response on any URL that countains a space character (ASCII 20)

Added by catmando over 9 years ago. Updated about 9 years ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:
Missing in 1.5.x:


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)

I'd appreciate if someone could confirm this.

Related issues

Related to Bug #1720: Rewrite/redirect rules and URL encodingNeed Feedback

Related to Bug #1802: url-encode/decodeFixed2008-10-20

Has duplicate Bug #1832: lighty doesn't quote spaces in urls in proxy moduleFixed2008-11-26

Has duplicate Bug #1819: mod_rewrite not working anymore after patchingFixed2008-11-11



Updated by catmando over 9 years ago

  • Target version set to 1.4.21

Updated by catmando over 9 years ago

Sorry in my rush i forgot to mention that this is in 1.4.20


Updated by peto over 9 years ago

There's no way this bug exists.

(And, er, ASCII 32, not 20.)


Updated by catmando over 9 years ago


Compare to:

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"] == ""{
url.rewrite-once = ( "^/(.*)$" => "/VirtualHostBase/http/$1")
proxy.balance = "hash"
proxy.server = ( "/VirtualHostBase" => ( ( "host" => "", "port" => 8001 ) ) )

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).


Updated by catmando about 9 years ago

  • Assignee set to darix

Updated by icy about 9 years ago

  • Status changed from New to Fixed

Should be fixed in r2362

Also available in: Atom