Ignore Content-Length header when setting 'chunked' for Transfer-Encoding

[jonathan343]

This PR removes the Content-Length header when a request is sent using chunked upload.

See the guidance below from Signature Calculations for the Authorization Header: Transferring Payload in Multiple Chunks for more details

When transferring data in a series of chunks, you must do one of the following:

Explicitly specify the total content length (object length in bytes plus metadata in each chunk) using the Content-Length HTTP header. To do this, you must pre-compute the total length of the payload, including the metadata that you send in each chunk, before starting your request.

Specify the Transfer-Encoding HTTP header. If you include the Transfer-Encoding header and specify any value other than identity, you must omit the Content-Length header.

For all requests, you must include the x-amz-decoded-content-length header, specifying the size of the object in bytes.

[codecov-commenter]

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

All modified and coverable lines are covered by tests ✅

Please upload report for BASE (develop@45da16d). Learn more about missing BASE report.
Report is 149 commits behind head on develop.

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

@@            Coverage Diff             @@
##             develop    #3360   +/-   ##
==========================================
  Coverage           ?   93.13%           
==========================================
  Files              ?       66           
  Lines              ?    14469           
  Branches           ?        0           
==========================================
  Hits               ?    13476           
  Misses             ?      993           
  Partials           ?        0           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[nateprewitt]