Re: Does Rack SPEC states that PATH_INFO must be cut after ";" (semicolon)?

["Iñaki Baz Castillo" <ibc@aliax.net>]

2009/12/1 Hongli Lai <hongli@phusion.nl>:
> On Nov 30, 5:27 pm, Iñaki Baz Castillo <i...@aliax.net> wrote:
>> Hi, could I get some reply to this mail please? I strongly think it could be a
>> bug in Rack so I can't understand why it is ignored.
>>
>> In fact, I've re-checked HTTP and URI BNF grammar and the semicolon ";" is an
>> allowed character into the URI path sections.
>
> As far as I know the Rack spec doesn't mention anything about ";".
> Neither do the CGI and WSGI specs for that matter:
> http://hoohoo.ncsa.illinois.edu/cgi/env.html
> http://www.python.org/dev/peps/pep-0333/

Yes, as I said I inspected the BNF grammar section for both URI and
HTTP specifications, and ";" is an allowed char into an URI segment.
But the fact is that Thin and Mongrel cut the PATH_INFO when finding a ";".

Unfortunatelly the author of Thin closed the bug:
  http://github.com/macournoyer/thin/issues/closed/#issue/6


-- 
Iñaki Baz Castillo
<ibc@aliax.net>