[squid-users] forward_max_tries 1 has no effect

[Ivan Larionov]

> 
> On Nov 23, 2017, at 12:32 AM, Amos Jeffries <squid3 at treenet.co.nz> wrote:
> 
> On 23/11/17 14:20, Ivan Larionov wrote:
>> Hello.
>> We have an issue with squid when it tries to re-forward / retry failed request even when forward_max_tries is set to 1. The situation when it happens is when there's no response, parent just closes the connection.
> ...
>> It doesn't happen 100% times. Sometimes squid returns 502 after the 1st try, sometimes it retries once. Also I haven't seen more than 1 retry.
> 
> Please enable debug_options 44,2 to see what destinations your Squid is actually finding.

I'll check this on Monday.

> 
> max_forward_tries is just a rough cap on the number of server names which can be found when generating that list. The actual destinations count can exceed it if one or more of the servers happens to have multiple IPs to try.
> 
> The overall transaction can involve retries if one of the other layers (TCP or HTTP) contains retry semantics to a single server.
> 
> 
> 
>> Could it be a bug? We'd really like to disable these retries.
> 
> Why are trying to break HTTP?
> What is the actual problem you are trying to resolve here?
> 

Why do you think I'm trying to break HTTP?

squid forwards the request to parent but parent misbehaves and just closes the connection after 40 seconds. I'm trying to prevent retry of request in such situation. Why squid retries if I never asked him to do it and specifically said "forward_max_tries 1".

And this is not a connection failure, squid successfully establishes the connection and sends the request, parent ACKs it, just never responses back and proactively closes the connection.

We're already fixing parent behavior, but still want to disable retries on squid side.

> 
> Amos
> _______________________________________________
> squid-users mailing list
> squid-users at lists.squid-cache.org
> http://lists.squid-cache.org/listinfo/squid-users