Return-Path: X-Original-To: apmail-trafficserver-users-archive@www.apache.org Delivered-To: apmail-trafficserver-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6B508D21B for ; Tue, 9 Oct 2012 09:44:12 +0000 (UTC) Received: (qmail 51387 invoked by uid 500); 9 Oct 2012 09:44:12 -0000 Delivered-To: apmail-trafficserver-users-archive@trafficserver.apache.org Received: (qmail 51187 invoked by uid 500); 9 Oct 2012 09:44:11 -0000 Mailing-List: contact users-help@trafficserver.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@trafficserver.apache.org Delivered-To: mailing list users@trafficserver.apache.org Received: (qmail 51159 invoked by uid 99); 9 Oct 2012 09:44:10 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Oct 2012 09:44:10 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of buaawkl@gmail.com designates 209.85.219.42 as permitted sender) Received: from [209.85.219.42] (HELO mail-oa0-f42.google.com) (209.85.219.42) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Oct 2012 09:44:03 +0000 Received: by mail-oa0-f42.google.com with SMTP id j1so5305864oag.29 for ; Tue, 09 Oct 2012 02:43:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=2jRfeXCibUQsTOa6hGHUc9hlMffZDEquj3dysi8EOWE=; b=Fgfft0xO1q+CYwbrih++HkB7u6T7IFRP3MFNdZBKb99IDBSWZq3IDFtm6bjP+StekO eF/0/w4KzO3eMWugBThQVnNLuTZtSGqMaiYrNzDkUTYgKTllmhO5enqcST113AmnFWPu EO39kDVqqBmmrs8gB99/Bp4yzjCS02kcaVUg6SHix7OoIZTaOxrLalCNj2vmQFY3/5d8 mPM98eGsBjn9uOygEjC9cPlzHkMktxLATVNz8GqunhLLMVsLzf8LU8LyyGI1QzT3ugAE 7Hrw5adiWmOzFjS2+/e/h+citVh/vBAYx3f5yxgH/dbJZMR8DsXPUpxVs90rBwQYJ2GO lqZQ== MIME-Version: 1.0 Received: by 10.60.169.134 with SMTP id ae6mr15844465oec.55.1349775821987; Tue, 09 Oct 2012 02:43:41 -0700 (PDT) Sender: buaawkl@gmail.com Received: by 10.60.169.147 with HTTP; Tue, 9 Oct 2012 02:43:41 -0700 (PDT) In-Reply-To: <7D664BE6CF058A4CB1A06984A7AA678F15EA751C14@SM-CALA-VXMB06A.swna.wdpr.disney.com> References: <7D664BE6CF058A4CB1A06984A7AA678F15EA751C14@SM-CALA-VXMB06A.swna.wdpr.disney.com> Date: Tue, 9 Oct 2012 17:43:41 +0800 X-Google-Sender-Auth: ndHiA-46wu-agHsJNNxmmfyz81s Message-ID: Subject: Re: read_while_writer question From: Conan To: users@trafficserver.apache.org Content-Type: multipart/alternative; boundary=bcaec550b36c65603e04cb9d2ca6 --bcaec550b36c65603e04cb9d2ca6 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable I don't think read_while_writer work on 3.2.x/3.0.x. https://issues.apache.org/jira/browse/TS-1433 On Fri, Jan 27, 2012 at 12:54 AM, Walsh, Peter wrot= e: > Hello all,**** > > I wanted to follow up and see if anyone has had success with the > read_while_writer feature. We are currently using version 3.0.1. Any > thoughts or advice would be greatly appreciated.**** > > Thanks!**** > > ** ** > > Pete Walsh**** > > Software Engineer**** > > ** ** > > *From:* users-return-1309-Peter.Walsh=3Ddisney.com@trafficserver.apache.o= rg[mailto: > users-return-1309-Peter.Walsh=3Ddisney.com@trafficserver.apache.org] *On > Behalf Of *Walsh, Peter > *Sent:* Tuesday, January 24, 2012 10:03 AM > *To:* users@trafficserver.apache.org > *Subject:* read_while_writer question**** > > ** ** > > Hello,**** > > I'm trying to get the "read while writer" feature working but am seeing > some behavior I was not expecting or perhaps I just don't understand how > its supposed to work. I saw a couple other threads regarding this but > didn't see any clear resolution or open bugs for this in JIRA.**** > > ** ** > > I configured ATS to use the following settings=85**** > > ** ** > > CONFIG proxy.config.cache.max_doc_size INT 0**** > > CONFIG proxy.config.cache.enable_read_while_writer INT 1**** > > CONFIG proxy.config.http.background_fill_completed_threshold FLOAT 0**** > > ** ** > > According to this link I found=85**** > > http://www.ogre.com/node/386**** > > ** ** > > To test this, I issued a request to a URI that I configured to wait 5 > seconds before responding. During the 5 seconds, I issued a second reque= st > to the same URI. In my wireshark capture, I observed the first request > going to the origin server and the second is blocked until the 1st > request's response is returned, but rather than reading the response from > cache, the second request then is made to the origin server. My > expectations (or maybe misunderstanding) was that the 2nd request would > read the response from cache once the 1st request's response is returned. > At this point re-issuing the request returns a cached response, so I kno= w > the response is cacheable.**** > > ** ** > > Any thoughts? Has anyone had luck getting this feature to work? **** > --bcaec550b36c65603e04cb9d2ca6 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable I don't think read_while_writer work on 3.2.x/3.0.x.

https://issues.a= pache.org/jira/browse/TS-1433

On Fri,= Jan 27, 2012 at 12:54 AM, Walsh, Peter <Peter.Walsh@disney.com&g= t; wrote:

Hello all,

I wanted to follow up and= see if anyone has had success with the read_while_writer feature.=A0 We ar= e currently using version 3.0.1.=A0 Any thoughts or advice would be greatly= appreciated.

Thanks!

=A0<= /span>

Pete Walsh=

Software E= ngineer

=A0

From: users-re= turn-1309-Peter.Walsh=3Ddisney.com@trafficserver.apache.org [mailto:users-return-= 1309-Peter.Walsh=3Ddisney.com@trafficserver.apache.org] On Behalf = Of Walsh, Peter
Sent: Tuesday, January 24, 2012 10:03 AM
To: users@trafficserver.= apache.org
Subject: read_while_writer question<= /span>

=A0=

Hello,

I'm trying to get th= e "read while writer" feature working but am seeing some behavior= I was not expecting or perhaps I just don't understand how its suppose= d to work. I saw a couple other threads regarding this but didn't see a= ny clear resolution or open bugs for this in JIRA.

=A0

=

I configured ATS to use the = following settings=85

=A0

= 
CO=
NFIG proxy.config.cache.max_doc_size INT 0
CONFIG proxy.config.cache.e=
nable_read_while_writer INT 1
CONFIG proxy.config.http.back=
ground_fill_completed_threshold FLOAT 0

=A0

According to this link I fou= nd=85

=A0

=

To test this, I issued a req= uest to a URI that I configured to wait 5 seconds before responding. =A0Dur= ing the 5 seconds, I issued a second request to the same URI. =A0In my wire= shark capture, I observed the first request going to the origin server and = the second is blocked until the 1st request's response is returned, but= rather than reading the response from cache, the second request then is ma= de to the origin server. =A0My expectations (or maybe misunderstanding) was= that the 2nd request would read the response from cache once the 1st reque= st's response is returned. =A0At this point re-issuing the request retu= rns a cached response, so I know the response is cacheable.

=A0

=

Any thoughts? =A0Has anyone = had luck getting this feature to work?=A0


--bcaec550b36c65603e04cb9d2ca6--