07-12-2012, 11:17 PM
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.
あなたの助けは非常に高く評価されるだろう。
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.
あなたの助けは非常に高く評価されるだろう。