Users can access PDF URLs that are encoded as one-time URLs or FTP

External Issue #8660489

Details

Created
Aug 26, 2016
Privacy
This issue is public.
Reports
Reported by 4 people

Sign in to watch or report this issue.

Steps to reproduce

The "Couldn’t open PDF…” issue is occurring because Edge does not like an application responding with inline (view in the browser) PDF content to an incoming POST request.

HTML Headers

Cache-Control: private
Content-disposition: inline; filename="voyager.pdf"
Content-Length: 0
Content-Type: application/pdf
Date: Wed, 24 Jun 2015 12:04:39 GMT
Expires: Wed, 24 Jun 2015 12:03:44 GMT
Server: Microsoft-IIS/7.5
Set-Cookie: LOGINDLLNAME=iAffordable; path=/
X-Powered-By: ASP.NET

EDGE should open inline PDF content to an incoming POST request.
The same exact request works in IE 9/10/11, Chrome and all other major browsers

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Jacob R.”

      Changed Status to “External”

    • We’re tracking this as a part of a larger feature to improve PDF navigation. Our team is investigating fixing this issue. Thanks for the feedback.

    • Microsoft Edge Team

      Changed Assigned To to “Derek L.”

    • I got here from This MS Connect Page

      I’m finding the same issue. Here’s my current code:

      protected void MyPdfMethod(object sender, EventArgs e)
      {
          // Returns ByteArray from a service
          var pdf = PdfService.GetPdf(@"/myFile.pdf");
          Context.Response.ContentType = "application/pdf";
      
          // As I understand - This should set the PDF to open in a new window.
          // Doesn't work for me though.
          Context.Response.AppendHeader("Content-Disposition", "inline; filename=myFile.pdf");
      
          // Then write the file out to the window.
          Context.Response.BinaryWrite(pdf);
      }

    You need to sign in to your Microsoft account to add a comment.

    Sign in