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

[Yuri]

Details. Squid's version, OS version, compiler version, core dump contents.


09.07.2017 22:59, bugreporter пишет:
> Hi,
>
> Is it allowed (supported) to chain icap and ecap services (using
> /adaptation_service_chain/)? I get a "FATAL: Received Segment
> Violation...dying." when trying to do it with some websites (www.linguee.com
> for instance). Each of those services works very well separately.
>
> Maybe this has never been tested before and I'm on a wrong way... But if (in
> theory) it's supported can someone help me to build the right squid
> configuration? I'll give more details on my configuration if the answer to
> the above question is YES.
>
> In a few words I'm trying to chain *c_icap/clamav* with  *squid-ecap-gzip*.
> Below my configuration:
>
>
>
>
>
> -----
> 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-tp4683033.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/20170709/1b81711d/attachment.sig>