Comment 1 for bug 1856303

The response is coming back as Transfer-Encoding: chunked - the 0 in the body is part of the transfer encoding chunked protocol indicating the length of the chunk is 0 (i.e. the body is empty)

I wasn't able to duplicate a transfer encoding chunked response on object 404 in-response to HEAD using the boto client on master or swift 2.18 (rocky release)

Can you provide more info

1) Does using another client (boto, aws cli, s3cmd, etc) to preform a similar request (HEAD to object that responds 404) results in the same transfer-encoding chunked response on this cluster?

2) Is the CloudBerry client sending any additional Content-Encoding aws-chunked request metdata or headers?