zuul-registry/zuul_registry
Ian Wienand ce2fb31a72 Fix range response
The range starts from zero, so we are returning one byte too many.
Docker echos this back to us in the manifest it uploads which is where
the extra byte is coming from.

This is actually the root cause of the off-by-one error worked around
in 134c942835.  A follow-on will clean
this up (Ibe061171bfd8ab6043b491bbab933bf277f8e12b).

Change-Id: I1fb1abf3c76ea8db7820caa90c97ddbf92997842
2021-09-13 08:23:37 -07:00
..
__init__.py Fix container image build 2019-10-02 13:50:42 -04:00
filesystem.py filesystem: add file syncs 2021-09-07 14:12:34 +10:00
main.py Fix range response 2021-09-13 08:23:37 -07:00
storage.py Add content-length headers and debug messages 2021-07-06 17:46:17 -07:00
storageutils.py Rework the stream_blob/stream_object API 2019-10-07 19:41:07 +00:00
swift.py swift: return size as int 2021-09-06 11:19:59 +10:00