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 912129915 for ; Mon, 23 Apr 2012 17:45:43 +0000 (UTC) Received: (qmail 49211 invoked by uid 500); 23 Apr 2012 17:45:43 -0000 Delivered-To: apmail-trafficserver-users-archive@trafficserver.apache.org Received: (qmail 48931 invoked by uid 500); 23 Apr 2012 17:45:38 -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 48897 invoked by uid 99); 23 Apr 2012 17:45:38 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Apr 2012 17:45:38 +0000 X-ASF-Spam-Status: No, hits=4.7 required=5.0 tests=FREEMAIL_FORGED_REPLYTO,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [98.139.52.232] (HELO nm13-vm0.bullet.mail.ac4.yahoo.com) (98.139.52.232) by apache.org (qpsmtpd/0.29) with SMTP; Mon, 23 Apr 2012 17:45:28 +0000 Received: from [98.139.52.190] by nm13.bullet.mail.ac4.yahoo.com with NNFMP; 23 Apr 2012 17:45:06 -0000 Received: from [98.139.52.169] by tm3.bullet.mail.ac4.yahoo.com with NNFMP; 23 Apr 2012 17:45:06 -0000 Received: from [127.0.0.1] by omp1052.mail.ac4.yahoo.com with NNFMP; 23 Apr 2012 17:45:06 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 893572.50881.bm@omp1052.mail.ac4.yahoo.com Received: (qmail 6842 invoked by uid 60001); 23 Apr 2012 17:45:06 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1335203106; bh=i98h0aAcSKkMeCKc5zLNlWBRYzsz7knMYbBBIqKyehA=; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=KmbXKDhZXUsHuiv9P5kGcYQ9HLo1AMC3KI1jBSF90ACX1vwZIFb2WlafvweC1yaKjxAzQlO0ooVrFVwzAAvJg1GljGdz6KlYWsTwhf4+OCAlyyDiVy/shY35rVCk/h18QKCRtoNlhriEgXNS6kQkdLRUaPsrvKLply7lVBFeLaU= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=FcSiUV5kLOIDdBeJShrVxmK4LpAKTyY31jdyunek/+TbJuMKYAFRgW3NKVt9dg9KeXFitFowloEQDSi0Si7NiNs8iBLaZwRKjNkBtDyORzKCoqfxYOk7rFHOrRtvg2CVnqSX2F0re8hF0vqM4CWDbCK7a7JVA7QjijMiv2RdhnM=; X-YMail-OSG: g1DsvasVM1n2tiR9fAnBNpEvjOsQjH1kcFDFH7p_vYa7WMh cAFSfHNiuIlkWinD7ia8HxZSma2Azm.lEmMk7JbVhIVqeiPalPCR43nF.W8_ .9EDIfmTzLfmq8KAkr0.qob56XWWp_RHepHPreMFHdXLPP9z4vcjPs951sCI KfJdw_LhdohzjAMB4bAL1j.FfGxm1BGFpwwrwaeCX.IyQHh75EB1U9p7R.Dk lCO0zRkl3o4j39.0WOvsCPwMfSwX1WYY3MpZcYIV.qLjiJGoXLNHI1XDkZAm ffTykR_kjW0wGeNKKRsL1YgTG4XNcXU_.6KYL7BZD8HFAVQlZViq4jhQP2Cf R5OOEA48yPnfmXfvwT.qkUD7jUocpWu.l8S1emloEPVBa8gtwDVmRRek6pDm nfklLnbQ_LKCMZAfEoZWC65Q_kHBvgbgvop7FYDAp5iB9EtIrT44cJO.aSHm H38YZmgwj_08BBqKTbQuo.SKattkn2Sa5Wbycqi1f6ycAzLfZxo3g5eN816G nUDffwJ2ChOtdFW3RbcrBrFbe Received: from [17.203.114.117] by web31803.mail.mud.yahoo.com via HTTP; Mon, 23 Apr 2012 10:45:06 PDT X-Mailer: YahooMailWebService/0.8.118.349524 Message-ID: <1335203106.91328.YahooMailNeo@web31803.mail.mud.yahoo.com> Date: Mon, 23 Apr 2012 10:45:06 -0700 (PDT) From: Bruce Lysik Reply-To: Bruce Lysik Subject: http byte range requests get cached and served from cache? To: "users@trafficserver.apache.org" MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="1502656925-197022122-1335203106=:91328" X-Virus-Checked: Checked by ClamAV on apache.org --1502656925-197022122-1335203106=:91328 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Hi guys,=0A=0ACan someone tell me the current state of ATS and http byte ra= nge requests?=0A=0AI have a system (libtorrent http seeding) that we put AT= S in front of. =A0Files are retrieved via 512k byte range requests for each= large file. =A0I would expect that after fully receiving a file, subsequen= t downloads via this mechanism would be cached. =A0I'm not seeing that in p= ractice.=0A=A0=0AI found this bug:=A0https://issues.apache.org/jira/browse/= TS-475=0A=0ABut I can't tell what the means to serving byte range requests = right now.=0A=0AAny help is appreciated.=0A=0A--=0ABruce Z. Lysik --1502656925-197022122-1335203106=:91328 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable
Hi guys,

Can someone tell me the c= urrent state of ATS and http byte range requests?
I have a system (libtorrent http seeding) that we= put ATS in front of.  Files are retrieved via 512k byte range request= s for each large file.  I would expect that after fully receiving a fi= le, subsequent downloads via this mechanism would be cached.  I'm not = seeing that in practice.
 
I found this bug= : https://issues.apache.org/jira/browse/TS-475

But I can't tell what the means to serving byte range requests right now.=

Any help is appreciated.

--
Bruce Z. Lysik <blysik@yahoo.com> --1502656925-197022122-1335203106=:91328--