Steps to reproduce
We’re observing on our website that when a user opens a PDF on our website that Edge is making two calls to our backend to retrieve the PDF data. The first call has the session and cookies that our site requires to print out the PDF, but that content returned never makes it to the browser. The second call seems like that one would show the content, but it has a different session. From searching it appears that this issue has come and gone with different IE Edge updates. This is not an issue in any other browsers.
Comments and activity
- Microsoft Edge Team
Changed Assigned To to “Venkat K.”
Changed Assigned To to “Manoj B.”
We have exactly the same problem with Edge. The missing session cookie in the second request prevents the correct pdf from being shown.
Works well in Firefox, Chrome, etc.
Anyone has a workaround for this bug ?
I have documented the same behavior in issue #16358526
I have even set up a test website, which nicely demonstrates the bug. Yes, two requests for each PDF is stupid, wasteful and slow. But the real problem is the second request does not pass the ASP.Net Session ID. This bug precludes the use of Edge with any website which renders PDFs on the fly based on data (like authentication tokens) stored in session variables.