-
Notifications
You must be signed in to change notification settings - Fork 229
Clarify the Range header on a chunked push response #581
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Clarify the Range header on a chunked push response #581
Conversation
@rchincha when Zot has a new release, let me know and I'll update that to resolve the failing checks. |
regclient/regclient#961 opencontainers/distribution-spec#581 Previously, zot returned the size of the currently uploaded chunk. Other registries the size of the entire blob. Align with the latter behavior. Signed-off-by: Ramkumar Chinchani <[email protected]>
regclient/regclient#961 opencontainers/distribution-spec#581 Previously, zot returned the size of the currently uploaded chunk. Other registries the size of the entire blob. Align with the latter behavior. Signed-off-by: Ramkumar Chinchani <[email protected]>
regclient/regclient#961 opencontainers/distribution-spec#581 Previously, zot returned the size of the currently uploaded chunk. Other registries the size of the entire blob. Align with the latter behavior. Signed-off-by: Ramkumar Chinchani <[email protected]>
e7ed8af
to
f3004a8
Compare
The update from Zot has been applied and this is ready for review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
This clarifies the Range header response should be the range of the entire blob and not the last received chunk. Signed-off-by: Brandon Mitchell <[email protected]>
f3004a8
to
d9f703c
Compare
I updated this to add the clarification on the GET response, and also to better identify the "response" part of the patch API. @mikebrow please include any further edits you would like to see. |
This clarifies the Range header response should be the range of the entire blob and not the last received chunk.
Fixes #580