Author orsenthil
Recipients hfuru, jerith, orsenthil, vstinner
Date 2010-11-21.15:11:24
SpamBayes Score 1.57368e-06
Marked as misclassified No
Message-id <20101121150949.GA1584@rubuntu>
In-reply-to <AANLkTinNs_Ts1B+S_Ye6PjGFqx_MihtA8U+t5-Rpsg6+@mail.gmail.com>
Content
On Sun, Nov 21, 2010 at 12:12:08PM +0000, Jeremy Thurgood wrote:
> I see your point now, but I don't agree with it completely. It seems
> reasonable to allow query parameters to specify things like sort
> order for a directory listing or have a fragment to focus the
> browser on a particular entry.

Can you please point me to some examples where such a kind of behavior
is exhibited or designed?

> On the other hand, if we don't want to support the
> redirect with a fragment or query parameters, we should instead return
> a 400 response. 

SimpleHTTPRequestHandler does not support REDIRECT on *a path* (any
path, directory or file, for that matter).  This bug was about a
primitive case where directory in the file system is not specified
with '/', it does a Hardcoded 301 redirect and adds a '/'.

>I can't see any situation in which redirecting
> "/something?foo" to "/something?foo/" is the correct behaviour.

As I explained, in the previous post, this would *not happen* in
practical scenarios, because code won't reach that point for valid
URLs.

> A 401 is "Unauthorized", which means the server is asking for
> authentication -- I don't think that's relevant here.

I am sorry, this was a typo.
It fails with -> urllib.error.HTTPError: HTTP Error 400: Bad Request
History
Date User Action Args
2010-11-21 15:11:25orsenthilsetrecipients: + orsenthil, hfuru, vstinner, jerith
2010-11-21 15:11:24orsenthillinkissue10231 messages
2010-11-21 15:11:24orsenthilcreate