RFC5987/RFC6266 Support (Content-Disposition headers)
|Reported by:||mnot@…||Owned by:||nobody|
|Cc:||jdunck@…, jreschke||Triage Stage:||Accepted|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
RFC6266, recently published by the IETF HTTPbis WG, describes a way to use the Content-Disposition header in HTTP in a manner whereby almost all current browsers can handle files (e.g., downloading with disposition 'attachment') that have non-ASCII characters in them, with other browsers using an ASCII fallback.
Django currently does not have an API for setting Content-Disposition, although there are a few references to it in the documentation. Adding such an API would allow Django sites to download files in any language easily.
Additionally, there's advice in the RFC that, properly implemented in a Django API, would help sites avoid common pitfalls.
For more information, see:
Change History (5)
comment:1 Changed 5 years ago by jreschke
- Cc jreschke added
- Needs documentation unset
- Needs tests unset
- Patch needs improvement unset
comment:2 Changed 5 years ago by aaugustin
- Component changed from Internationalization to HTTP handling
- Triage Stage changed from Unreviewed to Accepted