Compressed script files don't work when Edge debug console is open

Not reproducible Issue #9361788


Preston C.
Oct 15, 2016
This issue is public.
Found in
  • Microsoft Edge
Found in build #
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

This bug is exactly like except that it occurs in Edge and only occurs when the “Developer Tools” console is open.

  1. Have the console open in Edge
  2. Load a page with a script reference.
  3. Have the server send the script in a compressed gzip format (e.g. “.jsgz”)-- making sure that the server sets the correct Content Type (application/x-javascript) and the correct Content Encoding (gzip).
  4. The script fails to load with the error
    HTTP404: NOT FOUND - The server has not found anything matching the requested URI (Uniform Resource Identifier).

Now repeat the above steps with the Edge console closed, and observe that the script is correctly found and loaded.


0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Brad E.”

      Changed Assigned To to “Leo L.”

    • Hi Preston, do you have a site that reproduces this issue?  Thanks.

    • Microsoft Edge Team

      Changed Assigned To from “Leo L.” to “Fabio R.”

      Changed Assigned To from “Fabio R.” to “Mike J.”

      Changed Status to “Confirmed”

      Changed Assigned To from “Mike J.” to “Rob P.”

      Changed Status from “Confirmed” to “Not reproducible”

      Thank you for your feedback. I am unable to reproduce this issue at this time. 

      To attempt to recreate it, I have created a Node.js application consisting of an Express.js web server, serving files index.html and myscript.js from <root>/public using the Express Static middleware.  I then wired Express to send a GZIP-compressed stream in response to a GET request at /myscript.jsgz; I included sending headers of Content-Encoding: gzip and Content-Type: application/x-javascript (as well as several variations thereof).  I validated with Fiddler that the body of the response was actually compressed.  I was unable to observe any HTTP 404 errors, and the script always ran as expected, regardless of the condition of the F12 Developer Tools or Console.

      Your feedback is very important to us, and helps us improve the quality of Microsoft Edge.  We continue to welcome more feedback, and if you are able to provide us with a public website that we can use to observe this behavior, I will be happy to reactivate this bug.

      Best regards,
      The Microsoft Edge Team

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

    Sign in