Test #4531
Fetch registry content using API calls
Status:
NEW
Priority:
Normal
Assignee:
-
Sprint/Milestone:
-
Platform Release:
Tags:
Sprint:
Quarter:
Description
podman and docker are cli clients that already send some headers to the registry and have their own logic; a lot of people integrate with the registries by directly sending API calls where they define accept headers.
Verify that the correct content( if available of course) based on incoming headers.
This section might be helpful to understand how registry interprets incoming accept_headers and what it decided to return. https://docs.docker.com/registry/spec/manifest-v2-2/#backward-compatibility
Related issues
History
#1
Updated by kersom almost 2 years ago
- Description updated (diff)
#2
Updated by kersom almost 2 years ago
- Related to Issue #4314: accept_headers should be checked when docker pull is performed by digest added
#3
Updated by kersom almost 2 years ago
- Related to Test #4460: Test pull from container registry added
#4
Updated by kersom almost 2 years ago
- Subject changed from Fetch docker content using API calls to Fetch registry content using API calls
#5
Updated by rochacbruno almost 2 years ago
- Related to Test #4533: Test Pull Container Image by Digest added
#6
Updated by rochacbruno over 1 year ago
- Project changed from Pulp to Docker Support
#7
Updated by bmbouter over 1 year ago
- Tags deleted (
Pulp 3)
#8
Updated by ipanova@redhat.com about 1 year ago
- Project changed from Docker Support to Container Support
Please register to edit this issue