CODEWITHSUNDEEP
google-chromepdfiishttp-headers
Sumit Dobhal
Sumit Dobhal

Reputation: 151

Failed to load PDF document in Chrome

I have a PDF file stored on my server. I am unable to access the file using Google Chrome (or Ubuntu Chromium) via URL "sitename/pdfName.pdf"; while I am able to access the same PDF in Internet Explorer or FireFox without a problem.

Chrome is giving this error: "Failed to load PDF document"

Find attaching the error in this link Error Image.

Upvotes: 14

Views: 50046

Answers (4)

MeSo2
MeSo2

Reputation: 466

I had the same problem. In IIS I had to add this web.config file to my PDF folder to get it to work

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
    <system.webServer>
        <httpProtocol>
            <customHeaders>
                <remove name="Content-Type" />
            </customHeaders>
        </httpProtocol>
    </system.webServer>
</configuration>

You may also find that Chrome (on Ubuntu 19.04) has a problem with the header of the name: Content-Type value: charset=utf-8.

Upvotes: 0

Peter Arien
Peter Arien

Reputation: 21

When we encountered this problem, the only difference between PDF files that did and did not work was in the fist line of the PDF document itself. Here's the difference between the old PDF that caused the error and the fixed version as seen in a binary-enabled text-editor (in this case vim -b):

Original PDF file:

%PDF-1.6^M%<e2><e3><cf><d3>^M

Fixed PDF file:

%PDF-1.6^M
%<e2><e3><cf><d3>^M

So the problem was solved at the source, no need to burden the victims with installing extra software or reinstalling chrome.

I don't know if this is a problem with the PDF generator, or with the chrome plugin. According to the PDF specification the first line of a PDF document has to contain the PDF version, but it's not completely clear to me if the ^M is a valid line separator.

Upvotes: 2

user2728841
user2728841

Reputation: 1427

We had object:none in our security policy inside web.config, that was causing chrome to refuse to open it, and pressing f12 in chrome and then click "console" shows the error message.

Changing web.config security policy to object:self fixed the problem

In our case we could open PDFs in firefox and IE but not in Chrome, so Chrome has a stricter implementation of the security policies.

The below is a suggested edit which I have not tested:

You may also find that Chrome has a problem with the header of the name: Content-Type value: charset=utf-8. Removing it may fix it.

Also, as you are testing this, make sure that cache is not interfering with the response by keep on changing the request URL to something new sitename/pdfName.pdf?val=1 and then with the next test, ?val=2 and so on...

Upvotes: 5

liam
liam

Reputation: 2014

This might be due to Chrome’s built-in PDF Viewer not being able to open Firmex’s protected PDF document.

Try:

  1. Opening Google Chrome (obviously)
  2. In the top right, click More Untitled.png, then Settings.
  3. At the bottom, click Show Advanced Settings.
  4. Under Privacy, click Content Settings
  5. Under PDF Documents, check the box next to "Open PDF files in the default PDF viewer application."
  6. Once you have made the change, PDF files should open in Adobe Reader or Adobe Acrobat, rather than in Google Chrome.

Although it may not be ideal, it's a good alternative for now.

Upvotes: 0

Related Questions