PDF file not rendered at all

RESOLVED FIXED in Firefox 36

Status

()

Firefox
PDF Viewer
P3
normal
RESOLVED FIXED
5 years ago
3 years ago

People

(Reporter: Martijn Wargers (zombie), Unassigned)

Tracking

unspecified
Firefox 36
x86
Mac OS X
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [pdfjs-c-network][pdfjs-f-good-beginner-bug][pdfjs-f-fixed-upstream] https://github.com/mozilla/pdf.js/pull/5263, URL)

Attachments

(1 attachment)

(Reporter)

Description

5 years ago
Created attachment 807165 [details]
kortingscoupon_SEGH.pdf

This is with Firefox24 and on trunk.
The attached pdf file doesn't render at all for me, it just loads half way and then stops doing anything.
(Reporter)

Comment 1

5 years ago
As an attachment, the pdf renders just fine, so I guess this has something to do with the headers the server is sending on the url.

Comment 2

5 years ago
Same failure on windows.

Mozilla/5.0 (Windows NT 6.1; rv:27.0) Gecko/20100101 Firefox/27.0 ID:20130919030027 CSet: 70a765607344
Priority: -- → P2
Whiteboard: [pdfjs-c-rendering][pdfjs-f-regression]
The URL is WFM against Mozilla/5.0 (Windows NT 6.1; WOW64; rv:28.0) Gecko/20100101 Firefox/28.0 ID:20131202030201 CSet: 84a5a5800bd3 with PDF.js 0.8.751.
HTTP range that is coming from the server:

- Http: Response, HTTP/1.1, Status: Partial content, URL: /OFC/P83/3809/kortingscoupon_SEGH.pdf 
    ProtocolVersion: HTTP/1.1
    StatusCode: 206, Partial content
    Reason: Partial Content
    ContentLength:  132644
  + ContentType:  application/pdf
    Last-Modified:  Mon, 09 Sep 2013 08:22:00 GMT
    Accept-Ranges:  bytes
    ETag:  "087e3a735adce1:0"
    Server:  Microsoft-IIS/7.5
    XPoweredBy:  ASP.NET
    Date:  Mon, 02 Dec 2013 21:16:58 GMT
    Content-Range:  bytes 131072-132643/132644
    HeaderEnd: CRLF
  + payload: HttpContentType =  application/pdf

Per spec "When an HTTP message includes the content of a single range (for example, a response to a request for a single range, or to a request for a set of ranges that overlap without any holes), this content is transmitted with a Content-Range header, and a Content-Length header showing the number of bytes actually transferred."

Which means Microsoft-IIS/7.5 not properly sets Content-Length header for 206 response. See also http://support.microsoft.com/kb/2467528
Lowering priority: the workaround can be implemented to disable the range requests for Microsoft-IIS/7.5 server.
Priority: P2 → P3
Whiteboard: [pdfjs-c-rendering][pdfjs-f-regression] → [pdfjs-c-rendering][pdfjs-f-good-beginner-bug]

Updated

5 years ago
See Also: → bug 528807
Whiteboard: [pdfjs-c-rendering][pdfjs-f-good-beginner-bug] → [pdfjs-c-network][pdfjs-f-good-beginner-bug]
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Depends on: 1084158
Resolution: --- → FIXED
Whiteboard: [pdfjs-c-network][pdfjs-f-good-beginner-bug] → [pdfjs-c-network][pdfjs-f-good-beginner-bug][pdfjs-f-fixed-upstream] https://github.com/mozilla/pdf.js/pull/5263
Target Milestone: --- → Firefox 36
You need to log in before you can comment on or make changes to this bug.