#31082: New `Content-Disposition: inline` header in FileResponse causing issues
on
Safari
-------------------------------+--------------------------------------
Reporter: David Evans | Owner: nobody
Type: Bug | Status: closed
Component: HTTP handling | Version: 3.0
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Comment (by Carlton Gibson):
OK 👍
> I'm still slightly surprised by Safari's behaviour here. Given that
we're sending the correct Content-Type and Content-Encoding headers I
don't see why the filename should make any difference.
Hmmm. Yes. I don't see why the browser care what I call the file at all,
but... 🤷♀️
Thanks again for reporting the issue. Let's keep the communication
channels open. 😉
--
Ticket URL: <https://code.djangoproject.com/ticket/31082#comment:3>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.b8ad68334d387fea38b0f764d0b92ba2%40djangoproject.com.
