#17620: Chrome fails with additional Content-Disposition header
-------------------------------+--------------------
Reporter: jbauer@… | Owner: nobody
Type: Bug | Status: new
Component: Documentation | Version: 1.3
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------
Later versions of Chrome will fail to render content if you follow this
example by assigning an addition {{{ Content-Disposition }}} header, e.g.
{{{ response['Content-Disposition'] = 'attachment;
filename=somefilename.pdf' }}}
The Chrome browser returns:
'''Duplicate headers received from server'''
The response from the server contained duplicate headers. This problem is
generally the result of a misconfigured website or proxy. Only the website
or proxy administrator can fix this issue.
Error 349 (net::ERR_RESPONSE_HEADERS_MULTIPLE_CONTENT_DISPOSITION):
Multiple Content-Disposition headers received. This is disallowed to
protect against HTTP response splitting attacks.
--
Ticket URL: <https://code.djangoproject.com/ticket/17620>
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 this group at
http://groups.google.com/group/django-updates?hl=en.
