R. David Murray rdmur...@bitdance.com added the comment:
In this case I think it is safe enough, since it only results in the ;,= not
getting encoded. If an application were doing anything with the encoded chars,
it would probably be decoding them, and now that step will simply become a
Senthil Kumaran orsent...@gmail.com added the comment:
r87564 (py3k), r87565 (release31-maint) and r87566 (release27-maint).
Just a Note.
These kind of minor changes have many a times resulted in regression for
developers who relied upon previous bad behavior. I have added NEWS to explain
Senthil Kumaran orsent...@gmail.com added the comment:
I agree that semi-colon separated segments (params) can be in PATH portion of
the url. I was trying to find out, how a path;params would be useful in wsgiref
request_uri's PATH_INFO variable , wherein I assumed PATH_INFO should be a
R. David Murray rdmur...@bitdance.com added the comment:
If the RFC says they are safe it seems like we should include them in the safe
list.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10753
Senthil Kumaran orsent...@gmail.com added the comment:
On Wed, Dec 22, 2010 at 12:20:24AM +, R. David Murray wrote:
Presumably all that is needed is to add ';' to 'safe' in the call
that encodes PATH_INFO?
Well, that is what is required in order for the quote function call to
ignore it,
R. David Murray rdmur...@bitdance.com added the comment:
Well, if the parameters aren't part of the path info, what are they part of?
They are passed as part of path info now, just incorrectly encoded. I haven't
found anything so far to make me think they belong anywhere else.
--
New submission from Timothy Gates tim.ga...@gmail.com:
Consider the URL making use of the RFC1808 param syntax...
http://www/path;cookie=1234
The entire section '/path;cookie=1234' is passed in as PATH_INFO and so under
the request_uri implementation it will be quoted
import wsgiref
R. David Murray rdmur...@bitdance.com added the comment:
Presumably all that is needed is to add ';' to 'safe' in the call that encodes
PATH_INFO?
--
nosy: +orsenthil, pje, r.david.murray
versions: -Python 3.3
___
Python tracker
