----- Oryginalna wiadomość ----- > Od: "Roberto De Ioris" <[email protected]> > Do: "uWSGI developers and users list" <[email protected]> > Wysłane: sobota, 12 marzec 2011 8:15:08 > Temat: Re: [uWSGI] PATH_INFO > > Ok we have another "flaw" in WSGI spec :) > > CGI spec says that PATH_INFO should be decoded > WSGI says nothing, but as it does not mention REQUEST_URI as a > standard > variable we could have no way to determine (after decoding) if a / > was a / > or a %2F. > > In WEB-SIG i have found two discussion about it. But nothing really > definitive. > > We can assume that PATH_INFO must be decoded and REQUEST_URI not. > > Bu this is the current situation: > > nginx: REQUEST_URI->encoded PATH_INFO->decoded > cherokee: ->REQUEST_URI->decoded PATH_INFO->decoded > apache: REQUEST_URI->encoded PATH_INFO->decoded > uwsgi http router: REQUEST_URI->encoded PATH_INFO->encoded > > WSGI apps should not take in account REQUEST_URI and relay on > PATH_INFO, > so i think the best thing to do is decoding PATH_INFO in the uwsgi > http > router. > > Objections ? >
Probably it is all correct (not checked), but for me it looks like PATH_INFO was decoded twice. As a result the string has been corrupted. I added a picture illustrating the situation. So I rely on the REQUEST_URI, PATH_INFO and is mess. -- Łukasz Wróblewski http://www.nri.pl/ - Nowoczesne Rozwiązania Internetowe http://www.hostowisko.pl/ - Profesjonalny i tani hosting http://www.katalog-polskich-firm.pl/ - Najlepszy darmowy katalog firm
<<attachment: zrzut_ekranu.png>>
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
