I thought about the content-length again. The old V2 implementation wasn't able to handle unknown content-lengths. So does the V4. But I think it wouldn't be so difficult to add this. Because chunking is already implemented nicely and instead of sending the content-length of the complete payload, one could switch to transfer-encoding instead - like "Note"d here:
http://docs.aws.amazon.com/AmazonS3/latest/API/sigv4-streaming.html That would mean: Transfer-Encoding: chunked should do the trick and so omitting Content-Length completely. That would be really nice, since in our project we aren't always be able to get the complete content length in advance (live streaming from browser clients etc.). So in the worst-case, we have temporarily store the whole stream to disk (to get the content length) before we can send it to s3. What do you guys think? --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/678#issuecomment-103791927
