I've checked against the wsgiref module and you are most certainly correct:
unquoting PATH_INFO is the job of the wsgi server.
I'll being up the issue with with the aiohttp folks. Thanks for your time.
On Saturday, April 25, 2015 at 3:02:50 AM UTC-4, Florian Apolloner wrote:
>
>
>
> On Saturda
On Saturday, April 25, 2015 at 8:46:58 AM UTC+2, Matt Hooks wrote:
>
> I'm not really familiar with the design ideals of the Django devs or the
> WSGI spec. From what I can tell, the spec doesn't specify whether the url
> should be unquoted before passing it to the application.
>
I think the
Took me a few minutes to narrow down the right environment to recreate
this.
I'm seeing this "issue" with Gunicorn (latest version ,19.3.0), and only
when using the gaiohttp async worker (again latest version of aiohttp,
0.15.3). I've tracked it down to the troublesome line in aiohttp, but I
On Friday, April 24, 2015 at 10:51:12 PM UTC+2, Matt Hooks wrote:
>
> (The behavior of the development server is similar to the test client,
> although I haven't investigated for what exact reason.)
>
To be honest, even on my production machines I have this behavior -- so the
question is which
Hi all,
As I was fixing an issue in our API related to url encodings, I noticed a
problem should have been caught by a test that was somehow passing.
(Remember, make sure your test can fail!)
If you had some path /some/path/Spam%20Ham, and a URL pattern to capture
/some/path/(?P.+)$, it's not
