[squid-users] Bad HTTP requests trigger ICAP suspension

Silamael Silamael at coronamundi.de
Tue Dec 6 19:30:51 UTC 2016

On 06.12.2016 14:54, Amos Jeffries wrote:
> The exception was thrown from the HTTP request parser when handling the
> ICAP service response - which was delivering a new HTTP request message
> to use instead of the client-provided request message.
> Assuming your statement was correct about the input having '.' hostname.
> That means the ICAP changed the URL to 'scheme:///path'.

Hi Amos,

Now I got it. And Squid behaves exactly as I expected it.

> Nod. I think Eliezers solution with the ACL is the best thing to do
> while waiting on the Squid fix to handle that URL type. Maybe even keep
> it after that if the ICAP service is not liking the input request either.

That's what we are doing now.

Thanks a lot!

-- Matthias

More information about the squid-users mailing list