#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 David Evans):
Thanks Carlton, that's really helpful. I understand what's happening now
and I can see it's not a Django bug.
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.
I think I'll stick with the workaround I currently have for WhiteNoise
though as I prefer to maintain control over exactly what headers get sent.
Thanks again.
--
Ticket URL: <https://code.djangoproject.com/ticket/31082#comment:2>
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.979adb386cacbcbc8f9614bc3c134b3b%40djangoproject.com.
