| Hi, I think I may have found an issue: it only seems to ICAP the CONNECT request, whereas it will not pass any subsequent requests in that CONNECT tunnel to ICAP? So my original implementation did not check for the HTTP method in ICAP, so it returned the wrong CONNECT hostname: OPTIONS icap://10.10.0.119:1344/ ICAP/1.0 Host: 10.10.0.119:1344 Allow: 206 ICAP/1.0 200 OK Allow: 200,204 Connection: close Date: Thu, 04 Mar 2021 11:11:45 GMT Encapsulated: null-body=0 Methods: REQMOD,REQRESP Preview: 0 Transfer-Preview: * CONNECT ironpeak.be:443 HTTP/1.1 User-Agent: curl/7.64.1 Host: ironpeak.be:443 REQMOD icap://10.10.0.119:1344/ ICAP/1.0 Host: 10.10.0.119:1344 Date: Thu, 04 Mar 2021 11:11:23 GMT Encapsulated: req-hdr=0, null-body=84 Preview: 0 Allow: 204 ICAP/1.0 200 OK Connection: close Date: Thu, 04 Mar 2021 11:11:23 GMT Encapsulated: req-hdr=0, null-body=111 CONNECT //ironpeak.be:443/blog/big-sur-t2rminator/ HTTP/1.1 <<<< here is my bug Host: ironpeak.be:443 User-Agent: curl/7.64.1 But now, it does not pass any HTTP request in the CONNECT tunnel to ICAP: CONNECT ironpeak.be:443 HTTP/1.1 User-Agent: curl/7.64.1 Host: ironpeak.be:443 REQMOD icap://10.10.0.119:1344/ ICAP/1.0 Host: 10.10.0.119:1344 Date: Thu, 04 Mar 2021 11:19:00 GMT Encapsulated: req-hdr=0, null-body=84 Preview: 0 Allow: 204 ICAP/1.0 204 No Modifications Connection: close Date: Thu, 04 Mar 2021 11:19:00 GMT Encapsulated: null-body=0 ..TLS ciphertext.. <<<<. No more ICAP requests Any idea on how I pass -every- sslbumped request to ICAP? Thank you. Regards, On 4 Mar 2021, at 12:01, NgTech LTD <ngtech1ltd@xxxxxxxxx> wrote: Would it be possible to dump some icap traffic so we would be able to understand what might cause this issue if at all? Eliezer בתאריך יום ה׳, 4 במרץ 2021, 12:36, מאת Niels Hofmans <hello@xxxxxxxxxxx>:
|
_______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
