#29276: Compatibility of charset works not well when there are non-ascii
characters in HTTPResponse headers
-------------------------------------+-------------------------------------
Reporter: sanjiely | Owner: nobody
Type: Bug | Status: new
Component: HTTP handling | Version: 2.0
Severity: Normal | Resolution:
Keywords: HTTPResponse header | Triage Stage:
str bytes | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
Shouldn't HTTP headers only contain ISO-
8859-1 characters and [https://tools.ietf.org/html/rfc5987 RFC5987] be
followed to include parameters containing characters outside of its range?
I think your header should be something along.
{{{#!python
response['Content-Type'] = "attachment;
filename*=UTF-8''{}".format(quote(filename))
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/29276#comment:7>
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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.11b6be67a142722680c7b40eb896d91d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
