resource interpreted as document but transferred with mime type application/octet-stream pdf

8

votes

Don't know why I'm facing this issue not able to download pdf files in chrome browser, it is showing below error in Nginx server.

Though I have included mime type as application/pdf

1

votes

If it's just a warning then simply ignore it! It's just Chrome.

If not, try to include MIME Type as application/octet-stream.

0

votes

try to use those examples in your code.

this is a classic one: if you can load localhost:8080/xyz123/PdfFile.pdf then write like this:

<iframe src="./xyz123/PdfFile.pdf"  title="title">
   <a href="./xyz123/PdfFile.pdf"> ... </a>
</iframe>

0

votes

Similar issue came up for me only for .pdf files. I changed the Application Pool's idenity to Network Service and it fixed the issue.

I am not sure why it worked as the response header still had the same Content-Type, but it worked.