I have developed a simple site which has <a href>'s which set a cookie and the server should serve a page appropriate to the cookie value.
In one environment I have tested it, it doesn't. It returns a cached copy of the page. A manual refresh will bring up the page (I have cleared the client cache). This environment has winGate (proxy/cache gateway server) installed.
I have inserted
Expires: Fri, 15 Dec 2000 12:27:49 GMT Pragma: no-cache Cache-control: no-store,no-cache,must-revalidate,post-check=0,pre-chec +k=0 Content-Type: text/html; charset=ISO-8859-1
<META Http-Equiv="Cache-Control" Content="no-cache"> <META Http-Equiv="Pragma" Content="no-cache"> <META Http-Equiv="Expires" Content="0">
I do not have access to the cache server config. to do further testing, but I think at this stage that it is the culprit.
Is this a "doh" moment ?
Is my choice of logic (using cookies like this) flawed ?
If I modify the logic so that instead of cookies, I use post/get to pass the users choice to the server, will this improve the reliability of the site to load the pages correctly ?
Why would a gateway not support http header cache directives ?
Anyway, any and all help is greatly appreciated.
In reply to Clash with cache by macPerl
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |