#16470: Make FileResponse set the Content-Disposition header
-------------------------------------+-------------------------------------
Reporter: mnot@… | Owner: nobody
Type: New feature | Status: closed
Component: HTTP handling | Version: master
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by GitHub <noreply@…>):
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"a177f854c34718e473bcd0a2dc6c4fd935c8e327" a177f854]:
{{{
#!CommitTicketReference repository=""
revision="a177f854c34718e473bcd0a2dc6c4fd935c8e327"
Fixed #16470 -- Allowed FileResponse to auto-set some Content headers.
Thanks Simon Charette, Jon Dufresne, and Tim Graham for the reviews.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/16470#comment:11>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/071.fde10929fa7f89491586601b696cd580%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
