mirror of
https://github.com/project-zot/zot.git
synced 2026-06-15 11:37:56 +08:00
Akash Kumar
9e13be8b61
* fix(api): support multipart range blob pulls Signed-off-by: Akash Kumar <meakash7902@gmail.com> * fix(api): tighten multipart range response - Drop the redundant deferred closeRangeReaders; the deferred cleanup registered when the slice is created already covers all paths. - Stop copying the request Accept header into each multipart part's Content-Type. Accept can be a list of media ranges (e.g. "application/octet-stream,*/*"), which is not a valid Content-Type and may confuse multipart parsers. RFC 9110 lets us omit it entirely. - Set Docker-Content-Digest on the partial-content response so range pulls expose the same header as a full GET. - Drop the over-broad build tag on routes_internal_test.go; the parser unit test does not need any extension build tags. Signed-off-by: Akash Kumar <meakash7902@gmail.com> --------- Signed-off-by: Akash Kumar <meakash7902@gmail.com>
zot
zot: a production-ready vendor-neutral OCI image registry - images stored in OCI image format, distribution specification on-the-wire, that's it!
Documentation for zot is located at: https://zotregistry.dev
Code of conduct details are here.
License
