On 4/7/20 8:48 PM, zrm wrote:
https://www.trustiosity.com/squid/cache-debug.log.xz
On 4/8/20 10:46, Alex Rousskov wrote:
I found the reason for the difference.
After the destination IP address of your apt requests fails Host header
validation, Squid marks the request as "not cachable":
On
On 4/8/20 10:46, Alex Rousskov wrote:
On 4/7/20 8:48 PM, zrm wrote:
https://www.trustiosity.com/squid/cache-debug.log.xz
I found the reason for the difference.
After the destination IP address of your apt requests fails Host header
validation, Squid marks the request as "not cachable":
I
On 4/7/20 8:48 PM, zrm wrote:
> https://www.trustiosity.com/squid/cache-debug.log.xz
I found the reason for the difference.
After the destination IP address of your apt requests fails Host header
validation, Squid marks the request as "not cachable":
> hostHeaderIpVerify: IP 151.101.248.204:80
Hello Louis,
thank you for your answer.
It is not my webserver. Am a user who wants to connect to the webserver.
I know that the certificate chain is incomplete.
As far as I know squid should be able to fetch the missing intermediate
certificates on its own with the help of Authority Information
This is a simple one.
The certificate chain of that website is incorrect.
As shown here :
https://www.ssllabs.com/ssltest/analyze.html?d=www.formulare%2dbfinv.de
Check you webserver first and correct you ciphers in your apache webserver.
Greetz,
Louis
> -Oorspronkelijk
Hello,
I use a self compiled squid 4.10 compiled as follow:
~# squid --version
Squid Cache: Version 4.10
Service Name: squid
This binary uses OpenSSL 1.1.1d 10 Sep 2019. For legal restrictions on
distribution see https://www.openssl.org/source/license.html
configure options: '--prefix=/usr'
