There are other problems in my project that are caused by "back caching" but I don't mean to tire you. As far as I can tell the only hope for an elegant solution to the above problem is to find a way to completely disable this type of caching altogether. I've been trying to inject in each web page displayed in IE11 a javascript block which will create and invoke a web worker which will simply sleep for ever and ever in its onmessage callback.
The logic behind this is that according to the docs a web page will not be cached if there is Web Worker still running the moment the user navigates away from it if I understand correctly. Still trying to overcome this obstacle if at all possible. Any feedback appreciated.
I should probably not reply here, as your project is beyond my experience. And other reason. That seems to be a hopeless limitation of webworker, as trying to fixup with document.
The dataurl trick seemed promising, but much as you say, it fired Security exception with other browsers. With IE11, the new webworker object was happily created from dataurl, but obviously wasn't running. Just silently fail. Object exists, but no clue why it doesn't operate. Oh well. This is my feedback. For purposes of backward compatibility with HTTP 1. However, the Pragma: no-cache header wasn't for this purpose.
According to the HTTP 1. It's intended for proxy servers that may prevent certain important requests from reaching the destination Web server. For future applications, the Cache-Control header is the proper means for controlling caching. Pragma: no-cache prevents caching only when used over a secure connection.
The page will be cached but marked as immediately expired. When the Cache-Control header needs to be used on non-ASP pages, it may be necessary to use options in the server configuration to add this header automatically.
For the process of adding HTTP headers to server responses for a particular directory, refer to your server document. For example, in IIS 4, follow these steps:. It's not a good idea to use this header globally across the entire Web server. Podcast Who is building clouds for the independent developer? Exploding turkeys and how not to thaw your frozen bird: Top turkey questions Featured on Meta. Now live: A fully responsive profile. Reducing the weight of our footer.
Related Hot Network Questions. Question feed. Stack Overflow works best with JavaScript enabled. Accept all cookies Customize settings.
Good luck Robert Aldwinckle Open a new IE Window, in that window open a new tab and type about:blank in the address bar Set up the dev tool so that its ready to capture events and network traffic 3.
Wednesday, December 14, AM. This was only recently improved in Java 9, but still not up to the speed of CBC and we are talking here way below 10mbits line speed " Regards. Wednesday, December 14, PM. Two years too late, but That message, viz.
See Mozilla's article on caching. I'd link to it, but site here doesn't let me. It would be nice if these Microsoft DOM warning codes were listed somewhere. Thursday, April 5, AM. IECustomizer said we can click on one and go to some docs. Here's another one Robert Aldwinckle
0コメント