Why does this URL result in a 400 (Bad Request) error?
is at rambler-co.ru
Wed Nov 4 00:53:37 MSK 2009
On Tue, Nov 03, 2009 at 09:44:17PM +0000, John Moore wrote:
> Igor Sysoev wrote:
> > On Tue, Nov 03, 2009 at 08:07:25PM +0000, John Moore wrote:
> >> Hello,
> >> I'm puzzled by a problem we've been getting with URLs like this:
> >> /webserviceakqa-geraldoflanagan_ais_JEzKjKps%2B0%2FAynL0G17OWg?line=cMyYNDWTMJCOFAMGPMHE
> >> nginx (version 0.6.35) is returning a Bad Request error, response code
> >> 400. The problem seems to be in the URL encoding of the string after the
> >> '_ais_' part - when there are no escaped characters (such as %2B), no
> >> error is returned. If it is a deliberate feature, is there some way I
> >> can bypass it?
> > In my tests 0.5.36, 0.6.39, 0.7.63, 0.8.22 try to open
> > "/path/to/webserviceakqa-geraldoflanagan_ais_JEzKjKps+0/AynL0G17OWg"
> > and return 404. You may try to set error_log to info level to see 400 error
> > reason.
> Thanks, Igor. It may just be to do with copying and pasting to the
> mailing list, but your URL is actually different - the problem section
> is not URL encoded ('JEzKjKps+0/AynL0G17OWg' instead of
> 'JEzKjKps%2B0%2FAynL0G17OWg'). It appears to be the URL encoding which
> is actually causing the problem.
I tested escaped URL "...s%2B0%2FA...", nginx unescaped it and tried to
open the file.
More information about the nginx