Hi again.
I'm back from struggling with squid and squidGuard, squirm and iRedirector..
I figured varnish on it's own IP, in front of apache with good rewriterules,
in front of zope, would be better after all, than the huge unwieldy squid
that was not meant for the purpose, combined with these external rewriters
with cryptic syntax, that where not meant for reverse proxying either...
Well, anyway, I've been playing with headers, vcl and the varnishtools, but I
can't quite figure out if there is a way to display what is beeing cached
_right_now_.
I realize I may be asking the wrong question, but to me that is the most
straightforward thing I want to know when trying to make a big site cachable.
Another thing.
Run-Time Parameters: auto_restart
Is that what it sounds like?
If I put "-p auto_restart=on" in /etc/sysconfig/varnish it will restart the
child prosess if it dies?
Regards
Gaute Amundsen
I'm back from struggling with squid and squidGuard, squirm and iRedirector..
I figured varnish on it's own IP, in front of apache with good rewriterules,
in front of zope, would be better after all, than the huge unwieldy squid
that was not meant for the purpose, combined with these external rewriters
with cryptic syntax, that where not meant for reverse proxying either...
Well, anyway, I've been playing with headers, vcl and the varnishtools, but I
can't quite figure out if there is a way to display what is beeing cached
_right_now_.
I realize I may be asking the wrong question, but to me that is the most
straightforward thing I want to know when trying to make a big site cachable.
Another thing.
Run-Time Parameters: auto_restart
Is that what it sounds like?
If I put "-p auto_restart=on" in /etc/sysconfig/varnish it will restart the
child prosess if it dies?
Regards
Gaute Amundsen