Is there any particular order to squid configuration??
Does this look correct?
I actually get allot of hits and it functions amazing, so I wanted to share
this in case I could improve something. Is there any issues with security? I am
concerned that an invasive container could become installed
On 2024-04-01 23:03, r...@ohmuro.net wrote:
after an upgrade from squid 5.4.1 to squid 5.9, unable to parse HTTP
chunked response containing whitespace after chunk size.
I could be wrong, but Can you please advise me know if there is a way or
patch to fix this issue.
The sender of these mal
On 2024-04-03 02:14, Loučanský Lukáš wrote:
this has recently started me up more then let it go. For a while
chrome is upgrading in-page links to https.
Just to add two more pieces of related information to this thread:
Some Squid admins report that their v6-based code does not suffer from
th
There is no way to configure around this. The error produced by Squid is
a hard-coded reaction to TLS level errors in the SSL-Bump process.
Squid needs some significant code redesign to do a better job of
handling the situation. Which I understand is already underway, but
still some way off us
On 2/04/24 16:03, root wrote:
Hi Team,
after an upgrade from squid 5.4.1 to squid 5.9, unable to parse HTTP
chunked response containing whitespace after chunk size. >
I think the following bugs were fixed and worked fine in squid 5.9 and
earlier.
https://bugs.squid-cache.org/show_bug.cgi?id=44
My effort so far:
acl SquidTLSErrorConnect ssl_error SQUID_TLS_ERR_CONNECT
##
#unsupported protocol definice
##
# define what Squid errors indicate receiving non-HTTP traffic:
acl foreignProtocol squid_error ERR_PROTOCOL_UNKNOWN ERR_TOO_BI
