Mailing-List: contact users-help@trafficserver.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@trafficserver.apache.org
Received-SPF: pass (athena.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding;
  b=sL4B1cPJE7CoVwNVIZVP+2rkjmfKwUk8axsIrRNwe1XgWJobS76rTH2FNX6nEvr5Pu3+VrJLenPTMqQI/GGi1ZgfzSBk1VUzKkWQpkMhRLxSBV7BPtejDKLNnmlWyKluVMLS4thILTtty17urNmBap4pFcauNnZNvvYqcfw6F5Q=;
References: <1335203106.91328.YahooMailNeo@web31803.mail.mud.yahoo.com>
 <4F95B0A7.9090404@apache.org>
Message-ID: <1335210876.62876.YahooMailNeo@web31803.mail.mud.yahoo.com>
Date: Mon, 23 Apr 2012 12:54:36 -0700 (PDT)
From: Bruce Lysik <blysik@yahoo.com>
Reply-To: Bruce Lysik <blysik@yahoo.com>
Subject: Re: http byte range requests get cached and served from cache?
To: "users@trafficserver.apache.org" <users@trafficserver.apache.org>
In-Reply-To: <4F95B0A7.9090404@apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

> Hi guys,=0A>> =0A>> Can someone tell me the current state of ATS and http=
 byte range requests?=0A>> =0A>> I have a system (libtorrent http seeding) =
that we put ATS in front of.=A0 Files are retrieved via 512k byte range req=
uests for each large file.=A0 I would expect that after fully receiving a f=
ile, subsequent downloads via this mechanism would be cached.=A0 I'm not se=
eing that in practice.=0A>> I found this bug: https://issues.apache.org/jir=
a/browse/TS-475=0A>=0A>Yeah, that's the "performance" issue.=0A>> =0A>> But=
 I can't tell what the means to serving byte range requests right now.=0A>=
=0A>Well, if all you see are Range: requests, and nothing ever fetches the =
full object, it never gets cached :/. Until we fix TS-475 though, I don't t=
hink anyone has cared about this problem, but there is at least one bug fil=
led about this (to trigger a background fill of the full object on a Range:=
 request, assuming of course the object is cacheable)=0A=0A=0AOkay, so if I=
 /do/ pull down the full object, the byte range requests will be served fro=
m cache? =A0I'm going to test that now. =A0=0A=0AThanks!=0A