Strange browser hickups with varnish

[Christian Wiese]

Hi JT,

thanks a lot for your answer and sorry for that late reply!
We found the problem in the vcl:

------------------------------------snip----------------------------------
 sub vcl_recv {
-	if (req.http.Cookie) {
+	if (req.request == "GET" &&
+		req.http.Cookie &&
+		(req.url ~ "/(images|res|inc)/" ||
+		req.url ~ "/slice/" ||
+		req.url ~ "/info/(resolveplaylist|cmenu)" ||
+		req.url ~ "/info/player/player.js" ||
+		req.url ~ "/info/streamchannel/getmetadata")) {
 		lookup;
 	}
------------------------------------snip----------------------------------

We currently test our application heavily, but everything looks fine so
far!

Thanks a lot to all people that made varnish happen :)

Cheers,
Chris

Am Tue, 17 Jun 2008 21:28:50 -0700
schrieb JT Justman <jt at endpoint.com>:

> Christian Wiese wrote:
> > The funny thing is that this seems to be a client thing. When I
> > have a browser hanging, I can fetch the same file with curl or wget
> > just fine.
> >
> 
> This could be due to Varnish having different versions in different 
> encodings (gzip/deflate/etc). Take a look at the encoding and see if 
> this is the cause of differences between browsers.
> 
> As to the larger issue, I don't have much idea, but I think you
> should post more information, at least your varnishlog output.
> 
> JT
>