Philip Jenvey wrote: >> Passing the slashes as %2f do not help: it seems that the stripping >> occurs after the URL decoding. >> >> Does anyone know where this stripping occurs and if it's possible to >> selectively disable it? > > Unfortunately you can't disable it, WSGI servers must decode the > URL's path portion before passing it to WSGI apps. Either an RFC or > the CGI spec (which WSGI 1 stays compatible with) mandates this, I > can't recall which -- Ben Bangert or Ian Bicking might remember.
It's in the CGI spec -- SCRIPT_NAME and PATH_INFO are url-decoded, so you can't distinguish between %2f and /. > All you can do is include that value as parameter instead, or use > WSGI 2 (which of course doesn't exist yet, but somewhere we've penned > this 'feature' to be removed in version 2 of the spec). It's mentioned as an issue that WSGI 2 could address, but there hasn't been any proposed solution. -- Ian Bicking : [EMAIL PROTECTED] : http://blog.ianbicking.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
