3 ms·
Most webservers have a way of adding a header# Content-disposition "attachment; filename=$1"; that forces downloads. Nginx at least guesses based on file exten
by mjevans 3y ago
Most webservers have a way of adding a header# Content-disposition "attachment; filename=$1"; that forces downloads. Nginx at least guesses based on file extension / mime type.
# https://stackoverflow.com/questions/9054354/how-to-force-file-download-in-the-browser-nginx-server https://stackoverflow.com/questions/9054354/how-to-force-fil...
# https://stackoverflow.com/questions/37131398/how-to-configure-nginx-server-which-download-any-files-in-derectory https://stackoverflow.com/questions/37131398/how-to-configur...
FYI - I've also recently run across end users who are likely victims of overzealous IT departments that disable Basic Auth, even on HTTPS connections. Even though they don't do anything to form fields which might contain the exact same data. I don't mind if they break their own domains but the whole Internet?
- aspyct 3y agoI have that header. Yet some personal iOS device decided to ignore it on safari. Don't know how, don't know why. Computers being computers.
- marcosdumay 3y agoFirefox used to have a settings screen where you could go file type by file type overriding the browser behavior and setting it to ignore Content-Disposition. Maybe Safari has something similar.