On Fri, 18 Mar 2011 10:36:27 +0100, Florian Friesdorf wrote:
> On Thu, 17 Mar 2011 15:10:56 -0500, Ian Bicking wrote:
> > It's implied by WSGI itself that the path be unquoted; there's no fix short
> > of changing the specification.
>
> What is WSGI's solution for path segments containing slashe
On Thu, 17 Mar 2011 15:10:56 -0500, Ian Bicking wrote:
> It's implied by WSGI itself that the path be unquoted; there's no fix short
> of changing the specification.
What is WSGI's solution for path segments containing slashes?
> On Thu, Mar 17, 2011 at 1:10 PM, Florian Friesdorf wrote:
>
> >
I'll just add that *if* you can design your URL space (you didn't just
inherit one), and you want to distinguish path segments from values that
contain '/', you can use URLs like:
/item/{some/value}/view
And then use the matching {}'s to figure out that "some/value" is one path
segment. This ma
On Thu, 2011-03-17 at 19:10 +0100, Florian Friesdorf wrote:
> I think paste.httpserver.WSGIHandlerMixin.wsgi_setup should not
> urllib.unquote the path before setting it in the wsgi environment
I'm afraid it must. This is something the WSGI specification inherits
from CGI.
Yes, it was a terrible
It's implied by WSGI itself that the path be unquoted; there's no fix short
of changing the specification.
On Thu, Mar 17, 2011 at 1:10 PM, Florian Friesdorf wrote:
>
> I think paste.httpserver.WSGIHandlerMixin.wsgi_setup should not
> urllib.unquote the path [1] before setting it in the wsgi en
