On Aug 8, 2013, at 12:56 PM, Sebastian Annies <sebastian.ann...@castlabs.com> wrote:
> Hi, > > So far I'm happy with everything except HTTP range requests. > Whenever the plugin is null-transforming a HTTP range request the > following is happening: > > * the return code is set to 200 (instead of 206) > * the content-range header is omitted > * nevertheless the plugin only 'sees' the requested bytes Hmmm, I tested this with 3.3.5, and I'm not able to reproduce. I'm running with the standard null-transform that comes in the examples/ directory. For example: loki (13:32) 424/0 $ curl -D - -o /dev/null -s -H "Range: bytes=0-100" -x localhost:80 http://www.ogre.com/~leif/ats/Screenshot%202013-07-11%20at%2012.46.21%20PM.png HTTP/1.1 206 Partial Content Date: Fri, 09 Aug 2013 19:32:20 GMT Server: ATS/3.3.5-dev Last-Modified: Thu, 11 Jul 2013 18:52:25 GMT ETag: "51ab-4e140e52805cd" Accept-Ranges: bytes Content-Length: 101 Content-Range: bytes 0-100/20907 This seems exactly as expected (and I get the same result without the null-transform.so plugin). More details on how to reproduce this ? Are you serving out of ATS's cache, or is it fetching from origin ? (My test fetches from Origin, because the default null-transform.so doesn't apply to cache hits). -- Leif
