um, because i am teh crazy?
kidding aside, i was attempting to establish a baseline config from
which i could get a grasp of how varnish works through each
particular routine. i'll be the first to agree that it's not a
brilliant idea for production, but was rather hoping to have a solid
g
Tom Pepper <[EMAIL PROTECTED]> writes:
> From my experience, cutting and pasting the example out of the man
> page into the first working example seems to have issues (all of my
> hits came back in the logs with the same hash id when I had that
> routine as part of my vcl.)
Why did you even cut an
In message <[EMAIL PROTECTED]>, Tom Pepper writes:
>Hi Poul:
>
>Thanks for the suggestions. Removing this routine seems to have
>fixed my issues:
>
> sub vcl_hash {
> hash;
> }
>
Ahh yes, that wouldn't work, I overlooked that.
I think that may be the vcl(7) being
Hi Poul:
Thanks for the suggestions. Removing this routine seems to have
fixed my issues:
sub vcl_hash {
hash;
}
It appears, contrary to the vcl(7) manpage, to be different than the
functional default. Is there an updated routine which would better
match
"Poul-Henning Kamp" <[EMAIL PROTECTED]> writes:
> sub vcl_recv {
> set req.url = regsub(req.url, "?.*", "");
> }
You need to quote the ?...
DES
--
Dag-Erling Smørgrav
Senior Software Developer
Linpro AS - www.linpro.no
___
varnish-misc mailing li
In message <[EMAIL PROTECTED]>, Tom Pepper writes:
>HI Poul:
>
>Thanks for what should have probably been a glaringly obvious
>answer. I now have a somewhat more strange problem.
>1) client requests http://varnish:10080/ -- varnishd returns / off
>the backend correctly.
>2) client requests /
HI Poul:
Thanks for what should have probably been a glaringly obvious
answer. I now have a somewhat more strange problem.
My disturbingly simple vcl_recv routine is presently:
backend default {
set backend.host = "nyp-web-3.corp.razz.com";
set backend.port = "80";
}
sub vcl_recv {
In message <[EMAIL PROTECTED]>, Tom Pepper writes:
>1) log the request exactly as it came from the client. We use these
>logs to track which distinct widget in the wild was viewed.
Varnish will alway record the request exactly as received.
>2) instruct varnish to ignore the query parameters a
Hello all:
I'm using varnish to act as a front-end cache for yet another social
networking widget site. Our SWFs are presented with a tracking ID in
the URI request which allows us to know which instance of the same
widget in the wild is being viewed the most. The requests look like:
GET
