Form/JavaScript not working on IE 11 with error DOM7011

117,383

Solution 1

This issue occurs if the server sends a "Cache-control:no-store" header or sends a "Cache-control:no-cache" header.

Solution 2

This error occurred for me when using window.location.reload(). Replacing with window.location = window.location.href solved the problem.

Solution 3

I faced the same issue before. I cleared all the IE caches/browsing history/cookies & re-launch IE. It works after caches removed.

You may have a try. :)

Solution 4

I have seen exactly the same error, also with IE11. In my case the issue occurred when user clicked <button> element, which was inside <form> tags.

The issue was remedied, by placing the <button> outside of <form> tags.

Share:
117,383
eastboundr
Author by

eastboundr

Truth Sets You Free.

Updated on January 08, 2021

Comments

  • eastboundr
    eastboundr over 3 years

    The register button for our ASP.net form, which uses the __postback function stopped working on IE 11, from the developer console, it shows:

    DOM7011: The code on this page disabled back and forward caching. For more information, see: http://go.microsoft.com/fwlink/?LinkID=291337.

    Does anyone know how to get around with this? What is this caching thing and why does it mess up forms. I seen similar complaints about this from others.

  • trysis
    trysis almost 9 years
    I got this when my page sent "Cache-Control: public, max-age=0". I'm assuming it's because of the max-age=0.
  • Sergiy Seletskyy
    Sergiy Seletskyy over 8 years
    if you are not able to locate "Tools", enable Command bar by right click on the header of IE11 window
  • Irfan Yusanif
    Irfan Yusanif over 8 years
    what is the solution ??
  • BBaysinger
    BBaysinger almost 7 years
    I tried this to debug, and the warning still appeared.
  • Suhas Kulkarni
    Suhas Kulkarni over 6 years
    This answer is the explanation of the problem but the solution?
  • brianestey
    brianestey about 6 years
    The server is sending a Cache-control header, so the best solution is to change the server. Secondarily, you may be able to make a different request for the same content. For example, add "?random=" + Math.random() to each of your links.