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 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 WSGI spec somewhat follows the CGI spec which says: > Unlike a URI path, the PATH_INFO is not URL-encoded, and cannot contain > path-segment parameters. > > So to my understanding this seems to be a bug in whatever you use, no? > > Cheers, > Florian > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/0fa133ed-4006-4295-bded-ba29c18055c2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
