I thought this might be of interest:
http://wiki.apache.org/incubator/TrafficServerProposal
- ask
___
varnish-misc mailing list
varnish-misc@projects.linpro.no
http://projects.linpro.no/mailman/listinfo/varnish-misc
On Aug 8, 2008, at 12:20, Ian M. Evans wrote:
[]
So of course a cookie is attached to each page, image,
javascript and CSS file.
Since I assume that some of the main sites in need of Varnish would be
the high-traffic, digg-friendly, ad-supported, Analtyics-using sites
what's the way
On Aug 7, 2008, at 6:32 AM, Damien Sarazin wrote:
The rewriterules rules were written like this :
RewriteRule ^/test.html / [R=301,L]
For this rewriterule to work with Varnish you have to modify it like
that :
RewriteRules ^/test.html http://www.website.com/ [R=301,L]
It sounds like
On Aug 8, 2008, at 10:27 AM, Ian M. Evans wrote:
The only problem is that our cookies are set for / because even
though
this looks like a directory path:
/poll/vote/173
/poll is actually an extensionless PHP script and /vote/173 its
pathinfo.
The cookies don't care how the script is
On Oct 29, 2007, at 0:42, Poul-Henning Kamp wrote:
Can Varnish ReProxing like perlbal? Or is there any reproxy module
for
varnish ?
It would be trivial to implement in VCL, but I'm not usre I see the
point in bothering an expensive backend, just to learn from it that
a cheaper one
On Jul 4, 2007, at 12:23 AM, Christoph wrote:
I need to build a hierachical caching plattform. The Goal is, to have
multiple frontends that will expire in sync.
[...]
Is this possible with varnish?
I haven't tried it with varnish, but I think it should work if you
use Expires: ... rather
On Jul 2, 2007, at 7:26, Manuel Amador (Rudd-O) wrote:
I never insulted any of you.
You really should go see a therapist. Just tell him or her: People
think I'm a rude idiot - please help me.
In your weblog post you called Dag-Erling and Poul-Henning thin-
skinned. Rather than disagree
On May 11, 2007, at 1:55 AM, Dag-Erling Smørgrav wrote:
There was also some talk at some point of adding some kind of policy
check functionality - the ability to perform a secondary HTTP request
from VCL code, e.g. to check a user's credentials before serving a
cached document which requires
On May 7, 2007, at 11:42 PM, Poul-Henning Kamp wrote:
I usually run services like varnishd under daemontools/supervise. I
realize that varnish already have an option for running a supervisor
process, but all the same I'd like to have an option to not daemonize
so I can run varnishd my way.
