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 imagine that isn't terrible relevent here. 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. This leaves us with the possibility of changing behavior when moving among different WSGI servers. While any decent developer should know there will be differences when they reconfigure their stack, it might make sense to ensure consistency for this particular detail. The only concern would be backwards compatibility, but from what I can tell, most of the gunicorn worker types currently already behave this way**, along with uwsgi. I imagine the majority of people are using one of those, so I doubt any signficant number are relying on this behavior, but I dont have much to back that up with. I havent checked any other implementations, like mod_wsgi. I suppose this boils down to whether or not Django should be normalizing the url path (PATH_INFO) from the WSGI server, or should just go with whatever it is provided. (** All the ones I checked, specifically sync, eventlet and tornado. The gevent ones dont play nice with my python3 install.) On Friday, April 24, 2015 at 5:07:59 PM UTC-4, Florian Apolloner wrote: > > > > 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 "production" server you are using and which versions > of $stuff. > > 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/271b15b5-2ff0-49b2-a5eb-c87ed99a5b04%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
