|
|
 | | mozilla
|
| Whoo, a new patch for the Linux rendering system is in today's nightlies, causing it to (finally) be as fast as Communicator in most situations. (And faster in others -- resizing deeply nested tables, for example.) (24 years ago, 10-Aug-00, to lugnet.off-topic.geek)
| | | | | Re: Forced refresh of html pages instead of getting them from browser cache
|
| (...) Right, but telling your viewers to do that every time isn't a very viable option. (24 years ago, 10-Aug-00, to lugnet.publish, lugnet.off-topic.geek)
| | | | | Re: Forced refresh of html pages instead of getting them from browser cache
|
| (...) I'm not sure what you mean by cookies being set twice. The two functions above are used for non-logged in state and logged-in state respectively. Every page access while logged in causes the cookie to be set (notice they are not (...) (24 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
|
| (...) 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 (...) (24 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, (...) (24 years ago, 9-Aug-00, to lugnet.publish, lugnet.off-topic.geek)
|
|
