14.07.2017 23:17, Amos Jeffries пишет:
> On 13/07/17 22:22, Yuri wrote:
>> 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
On 13/07/17 22:22, Yuri wrote:
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
I can fully understand!
Warm 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-tp4683033p4683093.html
Sent from the Squid -
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
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
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.
And in general, making such statements, you need to be ready to prove
them in court.
When you can prove that we are
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
Hi Antony,
If they effectively don't *distribute* their modifications... But we don't
know. Thank you so much for the clarification.
Kind Regards,
-
Bug Reporter Contributor
OpenSource = Open-Minded
--
View this message in context:
On Wednesday 12 July 2017 at 10:55:36, bugreporter wrote:
> Thank you Yuri,
>
> The least I can say is that the conversation at
> http://bugs.squid-cache.org/show_bug.cgi?id=4597 makes me laugh a lot. My
> opinion is that if you modify the source code of an open source program
> without
Hi Alex,
Thank you for your post. I do appreciate your help and recommendations.
By chance, do you know another adapter that I can use to replace
squid-ecap-gzip. Actually I'm looking for an adapter capable to compress
HTTP contents.
Warm Reagrds,
-
Bug Reporter Contributor
OpenSource =
On 07/09/2017 10:59 AM, bugreporter wrote:
> Is it allowed (supported) to chain icap and ecap services (using
> /adaptation_service_chain/)?
Yes, it is allowed and supported.
> I get a "FATAL: Received Segment
> Violation...dying." when trying to do it with some websites (www.linguee.com
> for
Yup, seems this is
http://bugs.squid-cache.org/show_bug.cgi?id=4597
10.07.2017 13:45, bugreporter пишет:
Hi Yuri
,
Below the gdb backtrace. I hope that it could help you resolving the issue.
Regarding Squid-4.0 my understanding is that it is a beta version while I
need a stable version.
Hi Yuri
,
Below the gdb backtrace. I hope that it could help you resolving the issue.
Regarding Squid-4.0 my understanding is that it is a beta version while I
need a stable version. Actually at this stage upgrading to 4.0 would
represent a lot of integration, testing and validation work.
H. 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
And the gd backtrace:
Warm 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-tp4683033p4683040.html
Sent from the Squid
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
Also it can be issue with ecap-gzip adapter itself. AFAIK it has opened
issue with segfault on some sites.
Public version has not close this bug because of author abandoned project.
10.07.2017 0:54, bugreporter пишет:
> Thank you for your prompt response Yuri. Below information that you have
>
10.07.2017 0:54, bugreporter пишет:
> Thank you for your prompt response Yuri. Below information that you have
> requested:
>
> - Squid 3.5.26
> - Linux kernel 3.10.100 on an LFS (Linux From Scratch)
> - gcc-4.8.1, glibc-2.18
>
> Don't yet have a core dump. Are you interested in having the log
Thank you for your prompt response Yuri. Below information that you have
requested:
- Squid 3.5.26
- Linux kernel 3.10.100 on an LFS (Linux From Scratch)
- gcc-4.8.1, glibc-2.18
Don't yet have a core dump. Are you interested in having the log file in
debug mode?
Cheers
-
Bug Reporter
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
20 matches
Mail list logo
