As we're on the subject of supporting range requests, I have a substantive
patch at
https://github.com/SolidWallOfCode/trafficserver/tree/range
which attempts to fix the current range issue with alternates. This patch moves
the fragment offset table from the Doc header to the alternate info. Th
Monday, August 20, 2012, 10:54:31 AM, you wrote:
>> - does it cache partial objects (the parts corresponding to the requested
>> ranges) or the whole requested file?
ATS will only cache full object requests. It never caches range requests. If an
object has been cached in whole, then subsequent r
On Aug 20, 2012, at 2:29 AM, Bogdan Graur wrote:
> Thank you James for your answer!
I'll take a stab at the questions below. If I'm too egregiously wrong I hope
someone will step in and correct me ;)
>
>>
>> AFAIK range requests are working reasonably well in the 3.2 release. The
>> next ste
Thank you James for your answer!
>
> AFAIK range requests are working reasonably well in the 3.2 release. The
> next step that we would like is to be able to serve range requests out of
> the cache while the object is being cached; but for many (most?) cases the
> current support should be fine. Y
