+- Curl Global Community (https://communities.curl.com)
+-- Forum: Discussions (https://communities.curl.com/forumdisplay.php?fid=1)
+--- Forum: General Curl questions (https://communities.curl.com/forumdisplay.php?fid=2)
+--- Thread: forced applet resync (/showthread.php?tid=560)
forced applet resync - RobertShiplett - 07-12-2012
Is there a known problem with the effectiveness of the RTE setting to force applet resync ?
The Pale Moon browser cache shows 0 bytes, all applets are purged, a Curl change is made and the old applet appears (wrapped in HTML object element).
After reload has failed to show change, F5 on the HTML web page suffices to see the Curl code change.
The HTML wrapper is
<meta http-equiv="Pragma" content="no-cache" >
<meta http-equiv="Cache-Control" content="no-cache,no-store,must-revalidate,max-stale=0,post-check=0,pre-check=0" >
<meta http-equiv="Expires" content="-1" >
The browser is set to retain nothing as history. I wait to have the resync file fully one minute newer than the Curl file.
Any ideas? The -1 instead of 0 for Expires is from a Microsoft web page on IE. The meta setting are up even above the title in the HTML.
あなたの助けは非常に高く評価されるだろう。
RE: forced applet resync - wbardwell - 07-13-2012
The HTML wrapper header settings will not have any effect on the Curl applet on their own, it just tells the web browser to pretend that it got those headers with the HTML page. (If you also changed the URL to the applet in the HTML then it could help.) I think that something must still be caching the Curl applet. If the applet is purged from the Curl RTE, then it is not the RTE caching it. IIS will cache files sometimes, so it could be IIS's fault (other web servers do that too, you can test it by loading from the web server directly with telnet/cURL/wget/some other web browser.) It could also be that the web browser has cached the Curl applet, the best way to fix that is to configure your web server to send the proper Cache-Control headers (max-age=0 should be all that you need) for the Curl applet. It is also possible that you have a proxy in between the web server and the web browser, and proper Cache-Control headers often help in that case, but it depends on how the proxy is configured.