backport: clairctl: warn when range requests are not honored #2044
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
As discussed in quay#2029 the manifest generation is efficient only when HTTP "Range: bytes=0-0" header is well supported by the server. If not, the server might return the full layer, making the manifest generation very expensive. We warn the user in case their HTTP server does not support HTTP range requests. Signed-off-by: François Rigault <[email protected]>
hdonnay
approved these changes
Apr 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As discussed in #2029 the manifest generation is efficient only when HTTP "Range: bytes=0-0" header is well supported by the server. If not, the server might return the full layer, making the manifest generation very expensive.
We warn the user in case their HTTP server does not support HTTP range requests.