Additional information on this issue: I've discovered by virtue of a wireshark 
session that jclouds client is NOT sending chunked transfer-encoding, but 
rather aws-chunked content-encoding. Can anyone tell me why this is necessary, 
since A) it accomplishes the same thing that chunked transfer-encoding does 
(except that it's not compatible with most web servers' built-in ability to 
handle chunked encoding) and B) we're sending the content-length header?

Reply via email to