RE: URL Rewriting

2008-03-08 Thread Alex Harrington
Hi again Many thanks for all the help on and off list. I've tightened the regexp as suggested and am now setting req.url instead of req.http.url and It's working perfectly in the lab. Thanks again Alex sub vcl_recv { if (req.http.host ~ "^(www\.)?deansleisurecentre\.com$") {

Re: URL Rewriting

2008-03-08 Thread Dag-Erling Smørgrav
"Alex Harrington" <[EMAIL PROTECTED]> writes: > I'm hoping I can use Varnish to sit between the web server and my users > to disguise the subfolders in to separate domains - eg > > Client URL => Backend URL > http://example.com => http://example.com > http://example.com/index.phtml?d=12345 => > htt

URL Rewriting

2008-03-07 Thread Alex Harrington
Hi all I have a webserver over which I have no control. It's a managed CMS solution running Apache, however the vendor will not allow us to add URL rewriting rules or virtual hosts to the configuration. It serves different websites at the following URLs: http://example.com http://exampl

Re: URL rewriting / ignoring query parameters?

2007-09-11 Thread Tom Pepper
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

Re: URL rewriting / ignoring query parameters?

2007-09-11 Thread Dag-Erling Smørgrav
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

Re: URL rewriting / ignoring query parameters?

2007-09-11 Thread Poul-Henning Kamp
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

Re: URL rewriting / ignoring query parameters?

2007-09-11 Thread Tom Pepper
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

Re: URL rewriting / ignoring query parameters?

2007-09-11 Thread Dag-Erling Smørgrav
"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

Re: URL rewriting / ignoring query parameters?

2007-09-10 Thread Poul-Henning Kamp
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 /

Re: URL rewriting / ignoring query parameters?

2007-09-10 Thread Tom Pepper
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 {

Re: URL rewriting / ignoring query parameters?

2007-09-10 Thread Poul-Henning Kamp
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

URL rewriting / ignoring query parameters?

2007-09-10 Thread Tom Pepper
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