"Yu, Ryan" <[EMAIL PROTECTED]> writes:
> I'm having the strangest problem. I'm using varnish on some test
> servers and it works great when I run it on any random port number that
> is NOT port 80.
My guess is that there is some sort of content-scanning transparent
proxy between you and the serve
That could be true. I believe we are actually using Surf Control.
Would it be likely that this proxy would not affect Squid, yet would affect
Varnish?
I ask, merely because Squid appears to be working properly.
And I'd much rather use Varnish than Squid at this point and would like to find
a
Hi,
You could try and make a tcpdump of a slow session. "tcpdump -n -w
varnish.pcap -e "host $PROXYHOST" might show you what is going on. If
you have no success let me have a look.
Per.
Yu, Ryan wrote:
> That could be true. I believe we are actually using Surf Control.
>
> Would it be likely th
Hi
The gzip problem can be circumvented with since revision r1398.
Simply add the following to a varnish vcl script:
sub vcl_hash
{
if (req.http.Accept-Encoding) {
set req.hash += req.http.Accept-Encoding;
}
}
Denis Ahrens
__
In message <[EMAIL PROTECTED]>, Denis Ahrens writes
:
>Hi
>
>The gzip problem can be circumvented with since revision r1398.
>
>Simply add the following to a varnish vcl script:
>
>sub vcl_hash
>{
> if (req.http.Accept-Encoding) {
> set req.hash += req.http.Accept-Encoding;
