 | | Re: Forced refresh of html pages instead of getting them from browser cache
|
|
(...) BTW, the reason I *had* to figure out how to do this is because after uploading a file, the server spits out a javascript redirect (this.replace ...) to the folder url the uploaded to. If that page was cached, the user would see the cached (...) (25 years ago, 9-Aug-00, to lugnet.publish, lugnet.off-topic.geek)
|
| |
| | Re: Forced refresh of html pages instead of getting them from browser cache
|
|
(...) EXPIRES (...) Just a clarification, my example was for direct writing of HTTP headers, as you must do in a CGI. I suppose those tags would work as META HTTP-EQUIV tags in a web page, but I'm not sure if all proxy caches look at http-equivs, (...) (25 years ago, 9-Aug-00, to lugnet.publish, lugnet.off-topic.geek)
|
| |
| | Re: Forced refresh of html pages instead of getting them from browser cache
|
|
(...) That's a keystroke, right? A process runs to generate these pages quite frequently. We want the user to see the most freshly generated page without the user having to take any action of their own. So we want to put tags into the page to tell (...) (25 years ago, 9-Aug-00, to lugnet.publish, lugnet.off-topic.geek)
|
| |
| | Re: Forced refresh of html pages instead of getting them from browser cache
|
|
(...) <Ctrl> reload works for me. (25 years ago, 9-Aug-00, to lugnet.publish, lugnet.off-topic.geek)
|
| |
| | Re: Forced refresh of html pages instead of getting them from browser cache
|
|
(...) Wicked excellent. I'm going to try that. So the cookie rationale there is to avoid having cookies accidentally set twice, yes? In case one of the caching entities isn't smart enough to automatically not cache pages containing set-cookie (...) (25 years ago, 9-Aug-00, to lugnet.publish, lugnet.off-topic.geek)
|
