TIL Chrome can't download PDFs that are the result of a POST request. It opens inline but the download button fails with "Network error".
-
No content-disposition. Setting that to attachment works, as it bypasses the inline PDF display and goes straight to the download.
I think the problem is Chrome refuses to re-issue the POST request in response to the download button, but the error returned is useless.
-
-
Why should it reissue the request and not serialize it from cache?
-
Because we serve it as not cacheable, and it's too silly to realize this isn't really a "download" button but rather a "save" button.
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.