Don't set content-length header for HEAD requests with empty body #1067
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.
This extra function clause in
lib/ex_aws/operation/s3.ex
prevents thecontent-length
header from being added to the headers of aHEAD
request with an empty body (in which case the body of the request is an empty string and the value of that header would be "0").This is compliant with Amazon's specification of the HeadObject API endpoint, as it doesn't specify the
content-length
header as part of the URI Request Parameters.As an added benefit, this makes ExAws and ExAws.S3 work with Garage. Unlike Minio, Garage doesn't gracefully handle the extraneous presence of the
{"content-length", "0"}
header in the request headers of the HeadObject call.[x] Run
mix format
using a recent version of Elixir[x] Run
mix dialyzer
to make sure the typing is correct[x] Run
mix test
to ensure no tests have broken (also please make sure you've added tests for your particular change, where appropriate) (no new tests added)