[squid-users] Retry on connection refused.

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

Re: [squid-users] Retry on connection refused.

Precisely, when I send request to backend server, if server does not expose a target port yet, squid returns with 503 service unavailable. So I want to make squid retry until port is ready. With ''connect_retries" option, it is working in case of "No route to host". But if server exists but port i

[squid-users] Squid custom error page

Firefox 53.0.2 , Chrome 58.3029 y Opera 44 display "Proxy Server Refused Connection" page, instead of Squid custom error page, when connect to HTTPS site which blocked by proxy server. For example we try to connect to https://www.something.com via Squid proxy server which denied with 403 error this

Re: [squid-users] Squid custom error page

On 17/05/17 23:32, chcs wrote: Firefox 53.0.2 , Chrome 58.3029 y Opera 44 display "Proxy Server Refused Connection" page, instead of Squid custom error page, when connect to HTTPS site which blocked by proxy server. For example we try to connect to https://www.something.com via Squid proxy server

Re: [squid-users] Squid custom error page

W dniu 17.05.2017 o 13:32, chcs pisze: Firefox 53.0.2 , Chrome 58.3029 y Opera 44 display "Proxy Server Refused Connection" page, instead of Squid custom error page, when connect to HTTPS site which blocked by proxy server. For example we try to connect to https://www.something.com via Squid prox

Re: [squid-users] Squid custom error page

On 17.05.2017 16:04, Amos Jeffries wrote: On 17/05/17 23:32, chcs wrote: Expected Results: Display proxy server error page with deny info. This is a well-known problem with Browsers, they all refuse to display any response to a CONNECT tunnel message.

Re: [squid-users] Squid custom error page

Please note if you first let the connect tunnel to succeed (forcing bump) and then block the next coming request through that tunnel - you will get the blocked message displayed. We do it in ICAP (https://docs.diladele.com/faq/squid/cannot_connect_to_site_using_https.html) - other community me

[squid-users] list generates error messages ...

whenever I send a mail to the list, I get such an error message back from mailer-dae...@squid-cache.org This is the mail system at host lists.squid-cache.org. I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below. For further ass

Re: [squid-users] Squid to listen to HTTPS

Hi Alex, Thanks for the info. I updated Curl to a newer version that supports HTTPS and managed to access the SSL proxy. Much appreciated. Regards, Avi -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-to-listen-to-HTTPS-tp4682393p4682439.html Sent from

Re: [squid-users] Slow server ¿?

Hi. The server is serving web pages very slow. Not related to bandwith of delay pools... Thanks -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/Slow-server-tp4682400p4682440.html Sent from the Squid - Users mailing list archive at Nabble.com. ___

Re: [squid-users] list generates error messages ...

On 17.05.17 17:13, Walter H. wrote: whenever I send a mail to the list, I get such an error message back from mailer-dae...@squid-cache.org This is the mail system at host lists.squid-cache.org. I'm sorry to have to inform you that your message could not be delivered to one or more recipients.

Re: [squid-users] WARNING: All 20/20 negotiateauthenticator processes are busy.

Thanks, now i have "access denied"...why??? [root@squid ~]# squidclient -vv -h 192.168.1.215 mgr:info verbosity level set to 2 Request: GET cache_object://192.168.1.215/info HTTP/1.0 Host: 192.168.1.215 User-Agent: squidclient/3.5.20 Accept: */* Connection: close . Transport detected: IPv4-m

Re: [squid-users] WARNING: All 20/20 negotiateauthenticator processes are busy.

And if i do this http_port 127.0.0.1:3128 The i get this [root@squid ~]# squidclient -vv mgr:menu verbosity level set to 2 Request: GET cache_object://localhost/menu HTTP/1.0 Host: localhost User-Agent: squidclient/3.5.20 Accept: */* Connection: close . Transport detected: IPv4-mapped and IP

Re: [squid-users] WARNING: All 20/20 negotiateauthenticator processes are busy.

Sorry now squidclient it's working! was the ipv6. Thanks! -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/WARNING-All-20-20-negotiateauthenticator-processes-are-busy-tp4682362p4682444.html Sent from the Squid - Users mailing list archive at Nabble.com. __

Re: [squid-users] WARNING: All 20/20 negotiateauthenticator processes are busy.

On Wednesday 17 May 2017 at 20:41:06, erdosain9 wrote: > And if i do this > > http_port 127.0.0.1:3128 > > The i get this > > [root@squid ~]# squidclient -vv mgr:menu > verbosity level set to 2 > Request: > GET cache_object://localhost/menu HTTP/1.0 > Host: localhost > User-Agent: squidclient/3

Re: [squid-users] Slow server ¿?

On 2017-05-17 19:43, erdosain9 wrote: Hi. The server is serving web pages very slow. Not related to bandwith of delay pools... Thanks -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/Slow-server-tp4682400p4682440.html Sent from the Squid - Users mailing