Comment 11 for bug 900959

Hi Jay,

Yep that was my understanding too.

I was probably a bit loose in my terminology, causing the confusion - by the 'backend store' I meant the pre-existing remote HTTP or S3 or Swift image store location identified in the X-Image-Meta-Location URI provided on an image POST (i.e. without any further image content being uploaded to the store).

So I think we are actually on the same page re. the underlying problem. I should have a patch ready for submission soon, which will ensure the Content-Length is properly set on a GET of a cached remote issue.

Cheers,
Eoghan