PutMetadata updates Content-MD5 header if request was without done with Transfer-Encoding: chunked

[jkaniuk]

If request is done using regular HTTP PUT, without Transfer-Encoding: chunked, headers are properly set, original content is left intact, but Content-MD5 is modified to value of MD5 hash of empty string (PUT body).

If Transfer-Encoding is changed to chunked, everything works flawlessly.

Original node client uses chunked encoding to disable Content-length header.
However in other libraries Content-length header could be disabled regardless of encoding.