forked from TrueCloudLab/distribution
0818476cb1
Under certain cases, such as when putting a manifest or check for the existence of a layer, the status code checks in session_v2.go were too narrow for their purpose. In the case of putting a manifest, the handler only cares that an error is not returned. Whether it is a 304 or 202 does not matter, as long as the server reports success. Having the client only accept specific http codes inhibits future protocol evolution. Signed-off-by: Stephen J Day <stephen.day@docker.com> |
||
---|---|---|
.. | ||
v2 | ||
auth.go | ||
auth_test.go | ||
authchallenge.go | ||
config.go | ||
config_test.go | ||
endpoint.go | ||
endpoint_test.go | ||
httpfactory.go | ||
MAINTAINERS | ||
registry.go | ||
registry_mock_test.go | ||
registry_test.go | ||
service.go | ||
session.go | ||
session_v2.go | ||
token.go | ||
types.go |