Aha... thats it! - Thankyou Andreas! Yes we have some pipe employed as work arounds for issues with range requests, If-Modified-Since / e-tags, and some large download/streaming requests.
I put the suggested change in, and it has worked for the back-end selection problem just fine. I'm off to regression test the other reasons we had the pipe command in there, although it looks like a pretty straight-forward fix. Thanks again, Guy. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Andreas Plesner Jacobsen Sent: Friday, 11 November 2011 8:41 AM To: [email protected] Subject: Re: varnish incorrect back-end selection problem On Thu, Nov 10, 2011 at 09:35:05PM +0000, Guy Brodie wrote: > > * http tcp session re-use - the browser is re-using a single TCP session when > this happens, but I thought varnish inspects every request regardless - i.e. > it doesn't blindly pass an existing TCP session from the browser through to > the backend server it had previously selected… This can happen if you pipe. https://www.varnish-cache.org/trac/wiki/VCLExamplePipe -- Andreas _______________________________________________ varnish-misc mailing list [email protected] https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc _______________________________________________ varnish-misc mailing list [email protected] https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
