-
Notifications
You must be signed in to change notification settings - Fork 240
Conformance Test: 'Accept' header set during manifest put #396
Copy link
Copy link
Closed
Description
Within the OCI spec there is no mention of the 'Accept' header being set during put operations. Is it expected behaviour to have the Accept header set to 'application/vnd.oci.image.manifest.v1+json'?
The server I am currently testing will return 406 due to the endpoint not producing 'application/vnd.oci.image.manifest.v1+json', only 'application/json', and the server is responding strictly to the request.
Can you provide clarification on whether the conformance test is incorrectly setting this header or whether the server should be expected to produce 'application/vnd.oci.image.manifest.v1+json'.
Note:
The header isn't being set by the conformance test explicitly but the underlying resty client is setting it here.
Request:
~~~ REQUEST ~~~
PUT /v2/test-img-name/manifests/tagtest0 HTTP/1.1
HEADERS:
Accept: application/vnd.oci.image.manifest.v1+json
Content-Type: application/vnd.oci.image.manifest.v1+json
User-Agent: distribution-spec-conformance-tests
~~~ RESPONSE ~~~
STATUS : 406 Not Acceptable
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels