"Invalid or corrupted PDF files" is displayed

Attach (recommended) or Link to PDF file here: http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.144.7135&rep=rep1&type=pdf

Configuration:

• Web browser and its version: Chrome 72.0.3621.121 (Official Build) (64-bit)
• Operating system and its version: MacOS
• PDF.js version: PDF.js v2.0.673 (build: 31012570)
• Is a browser extension: Yes

Steps to reproduce the problem:

1. Click the above link

What is the expected behavior? (add screenshot) This is what I can see when I pasted chrome-extension prefixed url or reloading the error pdf page. (chrome-extension://oemmndcbldboiebfnladdacbdfmadadm/https://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.144.7135&rep=rep1&type=pdf)

What went wrong? (add screenshot) This is what I can see when click the above link

Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension): https://chrome.google.com/webstore/detail/pdf-viewer/oemmndcbldboiebfnladdacbdfmadadm

[simonhong]

I found the cause of this issue. The reason is requesting twice to server in a very short interval. To the second request, server redirects to downloadsexceeded.html instead of pdf content. So, pdf.js complains it’s invalid/corrupted pdf file. It’s maybe server’s DDoS protection I think.

Why two requests are issued when user clicks that link? First one is issued by browser for user click. Then, pdfjs extension intercepts header response and redirects to extension url. Then, one more requesting is issued by pdf.js.

I think we can improve this more. How about using the contents received from first request instead of requesting again? This is just an idea. (Sorry, if this idea doesn’t make sense. I don’t fully understand about pdf.js/extension implementation now.).

WDYT? @timvandermeij @Rob--W

[timvandermeij]

Closing since this seems to work again.