Closed Bug 1022833 Opened 11 years ago Closed 11 years ago

pdf.js display works only with #disableRange=true

Categories

(Firefox :: PDF Viewer, defect)

29 Branch
x86_64
Linux
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: karthi.amrita.cbe, Unassigned)

Details

Attachments

(2 files)

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:29.0) Gecko/20100101 Firefox/29.0 (Beta/Release) Build ID: 20140428193838 Steps to reproduce: Opened the following PDF in Mozilla 29.0 for Ubuntu 12.04 64 bit. (happens for many other PDF files too) http://abdaoui.free.fr/t/Modeles_de_canaux/comparison-channels_scme_scm_winner.pdf http://www.cept.org/files/1050/documents/winner2%20-%20final%20report.pdf Actual results: It did not load the PDF. The progress bar in PDF.js started and stopped in middle. Changed the URL to http://abdaoui.free.fr/t/Modeles_de_canaux/comparison-channels_scme_scm_winner.pdf#disableRange=true and pressed enter. Then again pressed Reload/Refresh button. The progress bar loaded fully and page is displayed. This error happens with many PDF files. Expected results: Without #disableRange=true, it should have worked.
Component: Untriaged → PDF Viewer
I cannot replicate an issue. Do you use a proxy server that might disable HTTP range requests or not properly handle that? Can you try the same documents without HTTP proxy or at different location?
Flags: needinfo?(karthi.amrita.cbe)
Yes. I am using http proxy server. I tested without proxy. First link open immediately. The second link opened only after 3 times reloading the url. Why won't it work with proxy?
Flags: needinfo?(karthi.amrita.cbe)
(In reply to Karthikeyan Natarajan from comment #2) > Yes. I am using http proxy server. > I tested without proxy. First link open immediately. > The second link opened only after 3 times reloading the url. > > Why won't it work with proxy? It works with HTTP proxies that properly handle HTTP range request. Could you provide more details about your proxy server, so we could replicate the issue, study how many people are using it and report the problem to its vendor?
This file contains the http headers captured using Live HTTP headers 0.17 addon in Firefox, while loading a PDF in PDF.js from this link. http://www.ieee802.org/16/liaison/docs/L80216-09_0064.pdf
HTTP Headers captured by Live HTPP headers 0.17 addon in Firefox while loading the following link using PDF.js http://www.ieee802.org/16/liaison/docs/L80216-09_0064.pdf#disableRange=true
I am using internet via squid proxy inside a college network with firewall. The proxy access is using port 3128. Without proxy, the firewall drops all requests. I have attached 2 files containing the HTTP headers 1) without disableRange 2) with #disableRange=true PS: It will be nice, if PDF.js has some preferences or firefox "about:config" preference for #disableRange.
(In reply to Karthikeyan Natarajan from comment #4) > Created attachment 8438228 [details] > headers from Firefox pdfjs without disableRange > > This file contains the http headers captured using Live HTTP headers 0.17 > addon in Firefox, while loading a PDF in PDF.js from this link. > http://www.ieee802.org/16/liaison/docs/L80216-09_0064.pdf Looks like this configuration of squid rejects any HTTP range request with "HTTP/1.0 403 Forbidden" response. (In reply to Karthikeyan Natarajan from comment #6) > I am using internet via squid proxy inside a college network with firewall. > The proxy access is using port 3128. Without proxy, the firewall drops all > requests. > I have attached 2 files containing the HTTP headers 1) without disableRange > 2) with #disableRange=true > > PS: > It will be nice, if PDF.js has some preferences or firefox "about:config" > preference for #disableRange. This will be implemented by https://github.com/mozilla/pdf.js/pull/4851 and will be available for Firefox 33(?). You can set boolean `pdfjs.disableRange` to true (and if you are using the pdf.js extension extensions.uriloader@pdf.js.disableRange).
Thanks a lot.
I believe all the concerns were already answered so I'm marking this bug as RWFM. Please re-open if it's still the case.
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: