Closed Bug 847020 Opened 13 years ago Closed 3 years ago

embedded pdf is not displayed

Categories

(Firefox :: PDF Viewer, defect, P4)

Product:
Firefox
Component:
PDF Viewer
Version:
19 Branch
Platform:
x86_64
Linux
Type:
defect

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: always-funny, Unassigned)

Details

(Whiteboard: [pdfjs-integration])

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:19.0) Gecko/20100101 Firefox/19.0 Build ID: 20130301163408 Steps to reproduce: Assume the following links "http://www.sosy-lab.org/~dbeyer/Publications/2010-FMCAD.Predicate_Abstraction_with_Adjustable-Block_Encoding.pdf" (public pdf) and "http://yaaf.no-ip.org:3000/attachments/download/2/test.pdf" (my pdf) Both links can be downloaded without any problem. However now try the following html code: <html> <body> <object width="100%" height="800" type="application/pdf" data="pdf" id="pdf_content"> <p>Your browser does not support embedded pdf! Click <a href="pdf">here</a> to download the file.</p> </object> </body> </html> Can somebody bring some light over this behavior? Is this a bug or by design? If it is by design how can you possibly build a site with embedded pdf where the pdf should not be available for the public (for example it is only embedded after login)? NOTE: For this specific pdf no login is required but in Firebug I can see that a cookie is given to my webserver on download, while this cookie is not given when firefox is requesting the embedded pdf. (I don't know if this is related though) Actual results: Try the html with both files and you can see that the public pdf works perfectly while my pdf doesn't. I can even reproduce this with chrome and IE. Expected results: Both pdf files should work as they can be downloaded too
Component: Untriaged → PDF Viewer
I guessing it is because the second link has a content-disposition of attachment.
Priority: -- → P4
Whiteboard: [pdfjs-c-integration]

The second link didn't work for me...

Whiteboard: [pdfjs-c-integration] → [pdfjs-integration]
Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.