id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
22721	Fallback encoding support on request.GET required for MSIE	hoha@…	nobody	"Originally described at https://github.com/tomchristie/django-rest-framework/pull/1590 before I realised this was a Django issue.

While testing a new system in pre-production we found a bug when MSIE was being used; basically, the way MSIE handles query strings are interesting, to say the least. System locale can have a say in how it's being sent in the request, previous website's encoding can have a say, heck, even from where you launch the browser session.

In our testing, MSIE did not urlquote the querystring, but instead sent it in what looked like raw latin1. The problem becomes, that if you access this query string through request.GET in a Django view, you can an encoding error, if you happen to be using Python 3.x. From my findings, this was introduced in Django 1.6, and worked correctly under Django 1.5 (at least according to the PR I did for Django Rest Framework showcasing this bug).

It seems to me that Django should have some fallback encoding support for this - even if we ignore the fact that MSIE really should be urlquoting the querystring.

Could it be that Django 1.6 somehow introduced a regression over Django 1.5?"	Bug	closed	HTTP handling	1.7-beta-2	Normal	wontfix		linovia kevin@…	Unreviewed	0	0	0	0	0	0