Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
Ģ Groups Home
Rack Development
Home
+ new post
About this group
Join this group
Message from discussion Does Rack SPEC states that PATH_INFO must be cut after ";" (semicolon)?
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Scytrin dai Kinthra  
View profile  
 More options Dec 5 2009, 5:54 pm
From: Scytrin dai Kinthra <scyt...@gmail.com>
Date: Sat, 5 Dec 2009 14:54:03 -0800
Local: Sat, Dec 5 2009 5:54 pm
Subject: Re: Does Rack SPEC states that PATH_INFO must be cut after ";" (semicolon)?
Print | View thread | Show original | Report this message | Find messages by this author
After going through the various handlers and routing middlewares, I am
unaware of any apps that modify the PATH_INFO in the way described.
The split of PATH_INFO at ';' seems to occur before the request hits
rack.

On Mon, Nov 30, 2009 at 16:42, Iņaki Baz Castillo <i...@aliax.net> wrote:

> 2009/12/1 Hongli Lai <hon...@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
> <i...@aliax.net>

--
stadik.net

 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google