Stop Microsoft Edge 14/15 from caching all the JS

By design Issue #12183794

Details

Author
Pushan B.
Created
May 30, 2017
Privacy
This issue is public.
Found in
  • Microsoft Edge
Found in build #
14
Reports
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

Hi,

The issue is with a eCommerce website for the checkout flow. All the JS and other assets are being cached at the browser level. I’ve tried adding the “<META HTTP-EQUIV="Pragma” CONTENT="no-cache">" and
<%
response.setHeader(“Cache-Control","no-cache”);
response.setHeader(“Pragma","no-cache”);
response.setDateHeader ("Expires", -1);
%>

but this doesn’t seem to solve or help with the issue. When I checked the debugger tab in developer tools, I can see the scripts being duplicated (for example: I can see login.js from cache and also from the server). FYI, we are using DWR3.

Looking for a solution for this. Any help is appreciated. Thanks in advance :)

Regards,
Pushan

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Steven K.”

    • Hi Pushan,

      This site is for reporting issues with the MS Edge browser itself and somewhat specifically for developers receiving Insider Windows 10 releases.  I think using a Java servlet combined with javascript to perform XHR requests is beyond the scope of this site.

      However, I will perhaps point you in the right direction.  :)

      Have you looked at the unique requirements for DWR with respect to cache control?  Perhaps the following link can be of use:

      https://directwebremoting.atlassian.net/browse/DWR-648

      Hope this helps,

      The MS Edge Team

    • Microsoft Edge Team

      Changed Status to “By design”

    • Forgot to mention, that if you find any issues with Edge’s functionality specifically please let us know.

    • Hi Steven,

      Thank you for the response and providing the link. We are trying with that and shall let you know the outcome.

    • Hi Steven,

      We updated the deployment descriptor in the java servlet container by initializing the DWR configurations as given in the above link using init-param, but that did not work.

      The issue still exists and we are seeing 2 javascripts in the response- one is 200 OK (from page load) and the other one is 304 Not Modified (from cache).

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

    Sign in