#19468: django doesn't encode request.path correctly in python3
---------------------------------+------------------------------------
Reporter: aliva | Owner: nobody
Type: Bug | Status: new
Component: Python 3 | Version: master
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+------------------------------------
Comment (by aaugustin):
I'm following up on Claude's comment on #14487 here, because it's more
related to this ticket.
> Django will still encode the URL's in UTF-8, so the decoding will
probably fail.
The most likely failure mode is a full latin-1 website where URLs aren't
URL-encoded. Then the behavior described above in "2) When an URL contains
non-ASCII characters..." will kick in.
> `settings.DEFAULT_CHARSET` is really about response encoding, not much
else (see #4380).
I beg to differ. `settings.DEFAULT_CHARSET` is both about request and
response encoding. It is used to decode GET and POST data in requests.
--
Ticket URL: <https://code.djangoproject.com/ticket/19468#comment:14>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit https://groups.google.com/groups/opt_out.
