On Jul 12, 12:40 am, Armin Ronacher <[EMAIL PROTECTED]>
wrote:
> Hi,
>
> ~flow wrote:
> > my hosting solution is called wsgiref, and its there to stay... unless
> > i discover a similar thing that performs better. maybe with an nginx
> > in front. no apache, no mod_xy.
Any good reason why you need to use wsgiref server and why Apache/
mod_xy is not an option?
If you want a pure Python WSGI server, Paste server and the WSGI
server broken out of CherryPy both perform better than wsgiref.
> > also of interest is that percent-escaping
> > trailing slashes doesn't help, either. to my understanding, percent-
> > escaping should cause a character to loose its meta-meaning---so you
> > can have e.g. `#`es and `?`s in your url. it's unintuitive that this
> > should work for anything *but* trailing slashes.
>
> WSGI provides the path info as unescaped value so there is no way to find
> out if the value was escaped or not. If this is here to stay I don't
> know, there are intentions to change it on the web sig.
As much as people were grumbling about wanting it changed, fact is
that the behaviour derives from CGI specification for which WSGI bases
certain things on, thus cannot be changed.
Graham
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"pocoo-libs" 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/pocoo-libs?hl=en
-~----------~----~----~----~------~----~------~--~---
