Pdf Content-Disposition: inline; download

 · Force to download a PDF when Content-disposition is inline. by Shedon» Sat am. Hi, My problem is then I need to force to download a pdf file even it goes as Content-disposition=inline. A popup window occurs and default pdf reader renders the doc.  · These are the headers being sent: Date: Tue, GMT Server: Apache/ (Win32) PHP/ Content-Type: application/pdf Content-Transfer-Encoding: binary Content-Disposition: inline;filename=bltadwin.ru Connection: Keep-Alive Keep-Alive: timeout=5, max= Content-Length: It's still prompting a download bltadwin.rus: 5.  · For example, if you have a PDF file and Firefox/Adobe Reader, an inline disposition will open the PDF within Firefox, whereas attachment will force it to download. If you’re serving bltadwin.ru file, browsers won’t be able to display it inline, so for inline and attachment dispositions, the .

Content-Type: application/pdf Content-Disposition: attachment; filename="bltadwin.ru" As you can see, the Content-Type is correct (PDF in our case, It can be any other if you are displaying any other mimetype), but a download prompt is forced with the Content-Disposition: attachment header. Following up on #, I would like to propose, that also PDF files are shown directly instead of forcing downloads.. This applies to two use cases: 1. Following a download link¶. When following a download link, image are sent with content-disposition: inline, while all other files are sent with bltadwin.ru the some browsers is able to render PDF files directly (Firefox, Chrome, Safari. Chrome and Firefox can download pdfs (generated from adobe and others) to my download folder but both refuse to display in the browser, saying the file cant be downloaded. The files display perfectly using ci3 with setheaders and force_download.

Content-Type: application/pdf Content-Disposition: attachment; filename="bltadwin.ru" As you can see, the Content-Type is correct (PDF in our case, It can be any other if you are displaying any other mimetype), but a download prompt is forced with the Content-Disposition: attachment header. The reason is that some versions of IE can't handle ("Content-Disposition", "inline;filename= ") This is because filename= was originally intended for the attachment disposition. Not all browser-based PDF viewers can handle it. The only solution I see is to allow access via a different url. Suppose you have a route to the pdf like: /pdf/view. If you use Response::download it automatically sets the Content-Disposition to attachment which causes the browser to download it. See this question for the differences between Content-Disposition inline and attachment.