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
Message from discussion Bug: WEBrick handler does not set the unescaped PATH_INFO
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
 
candlerb  
View profile  
 More options Mar 15 2009, 4:44 pm
From: candlerb <b.cand...@pobox.com>
Date: Sun, 15 Mar 2009 13:44:28 -0700 (PDT)
Local: Sun, Mar 15 2009 4:44 pm
Subject: Re: Bug: WEBrick handler does not set the unescaped PATH_INFO
On Mar 13, 6:13 pm, Sam Roberts <vieuxt...@gmail.com> wrote:

> > In that scenario, any middleware which alters PATH_INFO will also have
> > to be careful to make corresponding changes to rack.path_info. Another

> Probably, though it might depend on why the middleware is modifying
> the env. I'd think doing so would generally be a bad idea.

Rack::URLMap is the canonical example.

> > So the only characters which cannot appear unencoded are / ? # [ ]

> And %.

You (and Ryan and Christian) are right of course. It really has to be
one thing or the other.

Aside: since this is Ruby we're talking about, we're not limited to
just strings. For example, PATH_INFO could be defined to be an array
of path components. Probably doesn't make life easier for anyone
though, compared with just having the original path available.

Regards,

Brian.


 
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.