In my experiments, I've run into a long(ish) delay when I ask for a
url behind http auth:
$ time wget -S http://www.koldfront.local/stats/
[...¹]
real0m16.799s
[...]
Going directly to Apache:
$ time wget -S http://www.koldfront.local:8080/stats/
[...²]
real0m0.013s
[...]
I have
In message [EMAIL PROTECTED], Adam =?iso-8859-1?Q?Sj=F8gren?= writes:
On Sat, 31 Mar 2007 17:17:10 +, Poul-Henning wrote:
Which version of Varnish are you running ?
The one from Debian unstable backported to stable, i.e. 1.0.3:
13 VCL_call c fetch
13 VCL_return c pass
Hmm,
In message [EMAIL PROTECTED], Adam =?iso-8859-1?Q?Sj=F8gren?= writes:
On Sat, 31 Mar 2007 18:18:36 +, Poul-Henning wrote:
Hmm, you're running into a bug in the pass implementation which
have since been fixed.
Ah, great.
(Where can I read about meaning of these? I have scanned through
On Sat, 31 Mar 2007 19:22:37 +, Poul-Henning wrote:
if (req.http.authorization) {
Should have been: req.http.authenticate
Well, no such header is ever sent, from what I can see, but I'll give
it a go.
No difference - still ~16s delay.
First the browser asks for the page and the server
Hello,
I had a smilar issue testing varnish last friday,
the backend was sending a 302 with a Transfert-Encoding:chunked,
Using tcpdump i noticed that varnish was trying to open a new tcp
connection with the backend, 3 attempts were made (delay ~15s) before
varnish
gave up and forwarded back
