On 15 May 2012, at 00:50, Walsh, Peter wrote: > I've noticed it works for transformations on objects not served from cache, > however if the transformation is run on an object retrieved from cache I'm > not seeing chunked transfer encoding. > > Was that the intention?
OTTOMH, with a cached object you know the content-length, so why would you want to chunk it? > We have a use case in which we cache the untransformed objects, so for cache > misses our transformation runs on the fresh object returned from the origin > and we see chunked encoding, but on cache hits the transformation runs on the > cached untransformed object and we don't see the chunked encoding. Sorry, can't help you with that one. Is it getting returned with a content-length that's invalidated by your transform? What happens if your transform unsets it? -- Nick Kew
