RE: [squid-users] Timeouts details and Retry problems

First of all, thanks for your help.

So, here is the behavior that our tests show:
1) when connect_timeout < read_timeout
        => No retries. Response time = read_timeout

2) when connect_timeout > read_timeout
        => Always 1 Retry = 2 requests to the content server. Response time = connect_timeout + read_timeout

Could you give us details about this behavior?
Do you plan to add a retry property to the configuration?

Fabrice

-----Original Message-----
From: Henrik Nordstrom [mailto:hno@squid-cache.org]
Sent: mardi 25 mars 2003 08:47
To: Victor Tsang
Cc: Fabrice DELHOSTE; squid-users@squid-cache.org
Subject: Re: [squid-users] Timeouts details and Retry problems

Only by editing the source.

1. Make sure server side persistent connections are disabled in
squid.conf.

2. modify fwdCheckRetry() in forward.c to always return 0.

Regards
Henrik

Victor Tsang wrote:
>
> Is there a way to turn off such feature, or control the number of retry
> squid does?
>
> Thanks.
> Tor
>
> Henrik Nordstrom wrote:
> >
> > mån 2003-03-24 klockan 12.11 skrev Fabrice DELHOSTE:
> >
> > > So after installing Squid, we modified connect_timeout and
> > > read_timeout. We found configurations that works but we would like to
> > > understand precisely why. Moreover, due to our misunderstanding, we
> > > sometimes have strange effects such as double requests (or even more)
> > > to the content server whereas the application correctly receives the
> > > timeout error by sending only one request. Any idea?
> >
> > Squid automatically retries requests if the first attempt fails, to
> > increase the likelyhood of a successful reply. Depending on the
> > conditions there may be as much as up to 10 retries of the same request.
> >
> > The same is also done by most browsers.
> >
> > --
> > Henrik Nordstrom <hno@squid-cache.org>
> > MARA Systems AB, Sweden
Received on Tue Mar 25 2003 - 02:58:06 MST