Skip to content

Conversation

jacaru
Copy link

@jacaru jacaru commented Aug 10, 2017

This fixes iOS downloads for me, that is, before this change selecting "Download" from the context menu would not trigger the download in any iOS browser.

Unfortunately the download only succeeds in Safari Mobile.

Even using the download URL directly wont work in any browser other than Safari. It is as if other browsers are not aware of the file type and without knowing which application could handle the file beforehand, the download is refused. Checking the response headers, Content-Type is correctly set to the MIME type. The logs show a GET request that is cancelled in short order, and then a HEAD request to the same download URL which is not handled by the server.

@jacaru
Copy link
Author

jacaru commented Aug 10, 2017

My only idea is that Safari might be the only browser honouring the Content-Disposition header. Which by the way, its being sent as Content-Disposition:inline; filename="<filename>", shouldn't it be attachment instead of inline?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant