[squid-users] 503 service unavailable on connection refused

[Alex Rousskov]

On 05/22/2017 03:02 AM, Dominic Kim wrote:
> I have tested with squid 3.3, 3.5, 4.
> And the behavior were same.

When using Squid v3.5 or v4, please reproduce the problem using a single
HTTP transaction while collecting level-7 or higher debugging and then
post the corresponding (compressed) cache.log.

http://wiki.squid-cache.org/SquidFaq/BugReporting#Debugging_a_single_transaction

Alex.


> 2017-05-22 18:01 GMT+09:00 Dominic Kim:
> 
>     When I connect to a target server via squid, if server does not
>     exist, I get "No route to host" error.
>     And if server exist, but port is not opened yet, I get "Connection
>     refused" error.
> 
>     As per the definition of "connect_retries" option, it should retry
>     when connection attempt failed.
>     (reference: http://www.squid-cache.org/Doc/config/connect_retries/
>     <http://www.squid-cache.org/Doc/config/connect_retries/>)
> 
>     IMHO, in both the cases, connection attempts failed and it is
>     supposed to retry.
>     However, if I enable this feature, it only retries on "No route to
>     host" error.
>     In case of "Connection refused", I am getting 503 service
>     unavailable error immediately.
> 
>     Are there anyway to fix this behavior?
>     Kindly help me.
> 
>     Thanks
>     Regards
>     Dongkyoung
> 
> 
> 
> 
> 
> _______________________________________________
> squid-users mailing list
> squid-users at lists.squid-cache.org
> http://lists.squid-cache.org/listinfo/squid-users
>