interval?
Thanks
Regards
Dominic
2017-05-23 1:13 GMT+09:00 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
>
I have tested with squid 3.3, 3.5, 4.
And the behavior were same.
Thanks
Regards
Dongkyoung
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 i
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: h
if server exists but port is not ready yet, it does not work.
Thanks regards
Dominic
2017-05-17 16:30 GMT+09:00 Dominic Kim :
> Is there any way to make squid retry on connection refused instead of
> returning 503 service unavailable imm
Is there any way to make squid retry on connection refused instead of
returning 503 service unavailable immediately?
Thanks in advance.
___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users
I am quite a newbie to Squid proxy.
I am using it with default configuration by running this:
docker run --name squid -d --publish 3128:3128 sameersbn/squid:3.3.8-23
When I connect to backend server via squid, if backend server is not ready
yet, squid get connection refused error or other conne