Scenario : some people are using a cache to view my website. i make changes to the site and i want them to be available immediately. so, does anyone know of a way to push_content_from a web server to a squid cache?
_________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
Sometime on Feb 20, aaaaarrrgghhh assembled some asciibets to say:
Scenario : some people are using a cache to view my website. i make changes to the site and i want them to be available immediately. so, does anyone know of a way to push_content_from a web server to a
It can't be done. Web transactions are client initiated, not server initiated. Only thing that you can do is to have a short expiry for pages that you update often.
--- Philip S Tellis philip.tellis@iname.com wrote:
Sometime on Feb 20, aaaaarrrgghhh assembled some asciibets to say:
does anyone know of a way to push_content_from a web
server to a
It can't be done. Web transactions are client initiated, not server initiated. Only thing that you can do is to have a short expiry for pages that you update often.
hmmm..thought as much..but u nvr know! would it be possible to generate and send a cache_digest with the new content from an upstream cache? or is cache_digest generation and transmission a fixed interval process?
__________________________________________________ Do You Yahoo!? Yahoo! Sports - Coverage of the 2002 Olympic Games http://sports.yahoo.com
+++ kishor bhagwat [21/02/02 03:05 -0800]:
hmmm..thought as much..but u nvr know! would it be possible to generate and send a cache_digest with the new content from an upstream cache? or is cache_digest generation and transmission a fixed interval process?
No, but http meta-tags should mostly work. http-equiv: no-cache is what you need, I think.
Devdas Bhagat
Sometime Today, Devdas Bhagat assembled some asciibets to say:
with the new content from an upstream cache? or is cache_digest generation and transmission a fixed interval process?
No, but http meta-tags should mostly work. http-equiv: no-cache is what you need, I think.
:)
you need the meta tags (or http headers) to tell the browser not to use the cache, but the browser must hit the server first in order to get the page with the meta tags/headers, but of course, the browser won't hit the server, because it has the page cached, so you need to use meta tags (or http headers) to tell the browser not to use the cache, but...
-
aaaaarrrgghhh -
Devdas Bhagat -
kishor bhagwat
-
Philip S Tellis