[squid-users] Chaining icap and ecap services - FATAL: Received Segment Violation...dying.

[Yuri]

Hmmmm. Bases on this log, issue occurs in ICAP processing.

Most close to this:

http://bugs.squid-cache.org/show_bug.cgi?id=4597

As I can remember, this bug occurs on ECAP, not with ICAP. Configuration
was like you, chained ecap+icap services. Sadly, I can't show patch for
3.5, especially it was platform-specific dirty hack ;)

Can you try to reproduce this on 4.0.x Squid? This time I have not 3.5.x
running servers.

AFAIK, this issue was not occurs neither on 4.x nor on 5.x Squid's.


10.07.2017 4:22, bugreporter пишет:
> Yes I had some issue with ecap-gzip (related to chunked content) that I have
> already resolved by bypassing chunked content (I modified the code). Now I
> have no issue with ecap-gzip when it's used alone (without being in a
> chain).
>
> Herewith the log file (debug_options ALL,3):
> squid.gz
> <http://squid-web-proxy-cache.1019090.n4.nabble.com/file/n4683039/squid.gz>  
>
>
>
> -----
> Bug Reporter Contributor
> OpenSource = Open-Minded
> --
> View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/Chaining-icap-and-ecap-services-FATAL-Received-Segment-Violation-dying-tp4683033p4683039.html
> Sent from the Squid - Users mailing list archive at Nabble.com.
> _______________________________________________
> squid-users mailing list
> squid-users at lists.squid-cache.org
> http://lists.squid-cache.org/listinfo/squid-users


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://lists.squid-cache.org/pipermail/squid-users/attachments/20170710/43261365/attachment.sig>