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

[Yuri]

13.07.2017 5:13, bugreporter пишет:
> Hi Antony,
>
> If they effectively don't *distribute* their modifications... But we don't
> know. Thank you so much for the clarification.
We're not so brainless. Even we not threat GPL as religious dogma, we're
never distribute our solutions. Especially, as I said, this seems as
very close platform-specific (and platform is marginal), also, in fact,
this bug is gone in later branches. So we're don't care on this bug.
>
> Kind Regards,
>
>
>
> -----
> 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-tp4683033p4683087.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/20170713/a18cf968/attachment-0001.sig>