4 ms·
As was pointed out in a cousin comment, it's not necessarily the browser or the webserver configuration. SSL proxies -- corporate middleware -- have a habit of
by Filligree 3y ago
As was pointed out in a cousin comment, it's not necessarily the browser or the webserver configuration.
SSL proxies -- corporate middleware -- have a habit of breaking this way, by stripping the content-disposition field or similar.
- treadmill 3y agoLet the user talk to their IT department and have them reconfigure their snake oil so it's not broken?
- cxr 3y agoIt would have to be mangling both the Content-Disposition and Content-Type headers. If that's really happening (I have my doubts) and that's a client you want to continue supporting, then the next step would be limiting yourself to SingleFileZ-style ZIP payloads that can be as text/html.