Repository navigation
Check for 406 status code when handling referrers API endpoint response - #2026
Merged
imjasonh merged 1 commit intoOct 28, 2024
Merged
Conversation
Signed-off-by: Meredith Lancaster <[email protected]>
imjasonh
approved these changes
Oct 28, 2024
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
While using the remote.Referrers function with the Artifactory registry, I found the function was unexpectedly failing. Digging into the error, I found the registry was returning a 406 instead of a 404 when the
remote.Referrersfunction attempted to make a request to the referrers endpoint. Adding http.StatusNotAcceptable to the list of handled status codes intransport.CheckErrorfixed the problem for me.This PR adds
http.StatusNotAcceptableto the list of status codes handled by transport.CheckError. Since it is a 4XX error,remote.Referrersis able to fallback and try the manifests API endpoint.I had filed #1962 asking about this change but realized the change is small enough a pull request might be easier.