On 2024-02-02 17:36, Yvain PAYEN wrote:
I just sent you a Onedrive link to 2 pcap files, one for http request
and one for https request.
Thank you. The ICAP service you are using is sending a malformed ICAP
response to Squid. That ICAP response promises that there will be no
HTTP body in
I just sent you a Onedrive link to 2 pcap files, one for http request and one
for https request.
Regards,
Yvain PAYEN
Pôle Opérations & Technologies
Equipe Infrastructure système
T. +33 (0)5 57 57 01 85 (Poste 1185)
M. +33 (0)7 87 30 34 01
Absent tous les mercredi
Tessi France
Immeuble
On 2024-02-02 12:04, Yvain PAYEN wrote:
We don't use ssl_bump, icap service only analyze HTTP CONNECT requests
Great, that simplifies things a lot.
Adaptation::Icap::Xaction::noteCommRead threw exception: > check failed: readBuf.isEmpty()> exception location: ModXact.cc(1219)
stopParsing
> Do you use ssl_bump rules to decode affected HTTPS traffic? Or is your
> service supposed to analyze plain HTTP CONNECT requests?
We don't use ssl_bump, icap service only analyze HTTP CONNECT requests
I just compared the debug logs between http and https request and the icap
service is
On 2024-02-02 11:00, Yvain PAYEN wrote:
Hi Squid users,
I have an issue with an external icap service I have to use (from
Forcepoint).
This service is working great with squid v3 and v4.
Starting v5 (v6 also tested) the service only work with plain text http
requests, all requests for
Hi Squid users,
I have an issue with an external icap service I have to use (from Forcepoint).
This service is working great with squid v3 and v4.
Starting v5 (v6 also tested) the service only work with plain text http
requests, all requests for https content are allowed even if the website
On 2024-01-19 09:08, Arun Kumar wrote:
Sorry, due to organization policy not possible to upload the debug logs.
I really doubt your organization prohibits sharing information with
trusted parties. It is up to you whether to make me (or any other Squid
developer who is willing to help you)
Hi, thanks for your reply.
I have been looking at :
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cache-Control
*The stale-if-error response directive indicates that the cache can reuse a
stale response when an upstream server generates an error, or when the
error is generated
