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

[Yuri]

Apologies are accepted. No problems. We ourselves were not pleased that
we did not have enough time to write the correct and beautiful patch. At
that time it was quite an unpleasant problem. The bottom line is that
it's very specific and for me it's a big surprise that something similar
happened again on another platform. Fortunately, on current versions
there is no problem.


13.07.2017 13:38, bugreporter пишет:
> Dear Yuri,
>
> My goal is not to hurt anybody here and if you consider that I offended you
> (or rather your "sponsor") I apologize. So sorry! The fact of the matter is
> that the conversation at http://bugs.squid-cache.org/show_bug.cgi?id=4597
> caught my attention and it was the first time I saw such a discussion on an
> open source technical forum.
>
> Thanks to you and exchanges with others I understand better the GPL today.
>
> 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-tp4683033p4683090.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/de0b8e77/attachment.sig>