On Monday 12 July 2021 at 20:12:03, Marcio B. wrote:
> I have the following problem on my Squid 4.6 on Debian 10.
>
> Squid does not redirect the user to the error page when blocking an HTTPS
> url. On HTTP it works correctly.
Short answer - it can't.
Longer answer - browser requests https://th
I have the following problem on my Squid 4.6 on Debian 10.
Squid does not redirect the user to the error page when blocking an HTTPS
url. On HTTP it works correctly.
I don't use transparent proxy. The proxy is manually configured in the web
browser.
Here is my squid.conf configuration file:
htt
Hi,
I would like to know how to deactivate the "?" refresh_pattern filter ?
(As most web pages nowaday should use cache-control or expire, I guess the
correct usage of headers should be enough to permit us to cache requests
with "?" !?
Advice are welcome...)
For example for /cgi-bin/:
#refresh_pa
On Monday 12 July 2021 at 18:58:43, Alex Irmel Oviedo Solis wrote:
> Hello all, I'm trying to download a file from
> https://prodcont.seace.gob.pe
> SSLLabs review shows that server supports only TLS 1.0
> Any solution please?
If you're trying to download a specific file from a specific server,
Hello all, I'm trying to download a file from https://prodcont.seace.gob.pe,
it seems have an old version certificate, the error that shows squid is:
//---Begin of error
The system returned:
(71) Protocol error (TLS code: SQUID_ERR_SSL_HANDSHAKE)
Handshake with SSL server failed: error:142
