Expand allowed status codes#171
Conversation
POST /v2/<name>/blobs/uploads/?digest=<digest> should allow for 202 Accepted. All DELETE calls should allow 405 Method Not Allowed. Signed-off-by: Peter Engelbert <pmengelbert@gmail.com>
|
Should be noted that the current spec is not as permissive, but it will be factored into the rewrite |
|
glad we're testing for this. |
|
the maintainers had chatted about this in a call recently. While everyone noted that some of these response codes are being used just to mimic docker registry, they also noted that they really ought to be corrected in the original registry implementation. |
|
I'm not opposed to this conformance test, but might we track the conversation to have this aligned in the community, rather than only widening the conformance to make it green for more registries? |
|
FWIW this change is now reflected in the spec.md on master branch |
|
@jdolitsky are saying that this PR is no longer needed? or just that the spec has the language supporting this? |
|
@vbatts - the spec already contains language, so this PR should prob be merged |
|
closing this. we settled on final HTTP codes for 1.0 |
POST /v2/<name>/blobs/uploads/?digest=<digest> should allow for 202 Accepted.
All DELETE calls should allow 405 Method Not Allowed.
This PR resolves the following comment by @jdolitsky on issue 68. Resolving this issue will make several registries go green on the relevant workflows.