Build failed in Jenkins: 3.HEAD-ppc-MacOS-Leopard #39

See -- [...truncated 3798 lines...] sed \ -e "s%[@]DEFAULT_HTTP_PORT[@]%3128%g" \ -e "s%[@]DEFAULT_ICP_PORT[@]%3130%g" \ -e "s%[@]DEFAULT_CACHE_EFFECTIVE_USER[@]%nobody%g

Build failed in Jenkins: 3.HEAD-amd64-opensuse #196

See -- [...truncated 7101 lines...] Testing ../../src/StoreMetaMD5.h ...Ok. Testing ../../src/gopher.h ...Ok. Testing ../../src/StoreIOState.h ...Ok. Testing ../../src/TimeOrTag.h ...Ok. Testing .

Jenkins build is back to normal : 3.HEAD-amd64-FreeBSD-7.2 #1561

See

Build failed in Jenkins: 3.HEAD-ppc-MacOS-Leopard #38

See -- [...truncated 3798 lines...] sed \ -e "s%[@]DEFAULT_HTTP_PORT[@]%3128%g" \ -e "s%[@]DEFAULT_ICP_PORT[@]%3130%g" \ -e "s%[@]DEFAULT_CACHE_EFFECTIVE_USER[@]%nobody%g

Build failed in Jenkins: 3.HEAD-amd64-opensuse #195

See Changes: [Alex Rousskov] Do not reuse persistent connections for PUTs to avoid ERR_ZERO_SIZE_OBJECT. A compliant proxy may retry PUTs, but Squid lacks the [rather complicated] code required to protect the PUT request body

Re: [RFC] CONNECT and use_ssl cache_peer

On 11.09.2012 03:35, Alex Rousskov wrote: On 09/09/2012 08:12 PM, Amos Jeffries wrote: sön 2012-09-09 klockan 21:34 +1200 skrev Amos Jeffries: Henrik and I seem to disagree on this being a good idea being plugged into BodyPipe. But as I see it BodyPipe is where Upgrade, WebSockets and SSL-Bum

Re: ICAP connections under heavy loads

On 11.09.2012 03:06, Alex Rousskov wrote: On 09/09/2012 02:30 AM, Amos Jeffries wrote: IIRC the race is made worse by our internal code going timout event (async) scheduling a call (async), so doubling the async queue delay. Which shows up worst on heavily loaded proxies. True. Unfortunatel

Re: [PATCH] Do not reuse persistent connections for PUTs

> ons 2012-08-29 klockan 12:42 -0600 skrev Alex Rousskov: >> Hello, >> >> I saw bogus ERR_ZERO_SIZE_OBJECT responses while testing Squid v3.1, >> but the same problem ought to be present in v3.2 as well. >> >> A compliant proxy may retry PUTs, but Squid lacks the [rather >> complicated] code re

Re: [PATCH]proposal for a fake_strore_url helper wrapping.

On 11.09.2012 04:16, Eliezer Croitoru wrote: On 09/10/2012 05:39 PM, Alex Rousskov wrote: On 09/09/2012 04:08 AM, Eliezer Croitoru wrote: I took the url_rewrite helper and used what ever seems needed to create a url_store_rewrite helper. I also added the needed variables for the next step and

Re: [PATCH] Do not chunk Content-Range responses

On 08/24/2012 04:28 AM, Amos Jeffries wrote: > On 24/08/2012 4:30 p.m., Alex Rousskov wrote: >> Hello, >> >> When Squid forwards a response with a Content-Range header, >> ClientSocketContext::socketState() detects the end of the response >> range(s) and returns STREAM_*COMPLETE to >> ClientSo

Re: [PATCH]proposal for a fake_strore_url helper wrapping.

On 9/10/2012 7:44 PM, Alex Rousskov wrote: To be clear, I think we should not push dummy code (e.g., code after step #1 or #2) into Squid trunk. Others may overrule me, of course, but I do not recommend counting on that or fighting over it. I'm with youy on it. I just noticed that I didnt got y

Re: [PATCH]proposal for a fake_strore_url helper wrapping.

On 09/10/2012 10:16 AM, Eliezer Croitoru wrote: > On 09/10/2012 05:39 PM, Alex Rousskov wrote: >> When you think these changes are ready for commit, please include a >> proposed commit message. It is a good idea to do that even before the >> last stage, of course -- it tells us what the patch is s

Re: [PATCH]proposal for a fake_strore_url helper wrapping.

On 09/10/2012 05:39 PM, Alex Rousskov wrote: On 09/09/2012 04:08 AM, Eliezer Croitoru wrote: I took the url_rewrite helper and used what ever seems needed to create a url_store_rewrite helper. I also added the needed variables for the next step and freeing them where and if needed. this is a mor

Re: [RFC] CONNECT and use_ssl cache_peer

On 09/09/2012 08:12 PM, Amos Jeffries wrote: >> sön 2012-09-09 klockan 21:34 +1200 skrev Amos Jeffries: >> >>> Henrik and I seem to disagree on this being a good idea being plugged >>> into BodyPipe. But as I see it BodyPipe is where Upgrade, WebSockets and >>> SSL-Bump should be happening in a nod

Re: ICAP connections under heavy loads

On 09/09/2012 02:30 AM, Amos Jeffries wrote: > IIRC the race is made worse by our internal code going timout event > (async) scheduling a call (async), so doubling the async queue delay. > Which shows up worst on heavily loaded proxies. True. Unfortunately, the alternative is to deal with ConnOpe

Re: [PATCH]proposal for a fake_strore_url helper wrapping.

On 09/09/2012 04:08 AM, Eliezer Croitoru wrote: > I took the url_rewrite helper and used what ever seems needed to create > a url_store_rewrite helper. > I also added the needed variables for the next step and freeing them > where and if needed. > this is a more of a basic sketch. Please do not ma

Re: Failure ratio

mån 2012-09-10 klockan 15:11 +0100 skrev Konstantin Korsunov: > All working good, but some times 3 times per day I have next error: > > Failure Ratio at 1.02 > Going into hit-only-mode for 5 minutes... That means that an unexpected amount of the proxied requests have failed, and to avoid further