fix: Set Content-Length header on monolithic push session request #176
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.
Building on my testing of Google Cloud Artifact Registry from #175, I noticed that their registry requires
Content-Length
to be set for acquiring a monolithic push session:I don't see a downside to setting this for monolithic pushes even though it's not strictly defined as required (for monolithic pushes, only for chunked pushes) by the OCI Distribution spec.
I should also note that this matches the behavior of
oras-go
where this is working as expected.