Hey Moti, I had an example on my local git which also works with gzip and other stuff for BGU however I cannot find it now. From what I remember this worked with POST but only like an external acl helper. Ie blocking or allowing OK/ERR: https://github.com/elico/drbl-icap-service Any modification of the headers is a bit complicated. I can try to check/test it but it will take time. From what I see 5.0.4 is pretty stable however there are specific issues related to TLS 1.3. Eliezer ---- Eliezer Croitoru Tech Support Mobile: +972-5-28704261 Email: ngtech1ltd@xxxxxxxxx Zoom: Coming soon From: squid-users <squid-users-bounces@xxxxxxxxxxxxxxxxxxxxx> On Behalf Of Moti Berger Hi I have an environment with squid version 5.0.4 with ICAP server adapting requests by adding an header. When I'm trying to send a POST request with a body I'm having an issue of a stuck connection. What should the ICAP response look like? What I do is to reply like this:
Please assume the number in req-body=360 is correct (I trimmed here the content of the new header). As I said, I use 'Preview: 0' since I don't mind the body. The question is whether declaring the body starts at X (req-body=X) is OK even though I don't have a body to send? I think having req-null=X is bad since it probably tells squid that I decided the adapted request should have no body, but that's only a guess. When the ICAP doesn't adapt the request, everything looks fine. When it adapts the request I see that the POST request squid sends to www.dst-server.com doesn't contain the body. On the logs of the server behind www.dst-server.com I see an entry for the API request only after I abort the request I sent. I use python's requests module to make the request:
I'll highly appreciate any help. Thanks, Moti |
_______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
