Transfer-Encoding Header For PUT request to AWS S3

[MQZhangThu]

I used pre-singed url to PUT image to AWS S3. The PUT request did not work out, and the AWS S3 response is 501 Error, saying that "Transfer-Encoding: Chunked" Header is not implemented.

Anyone knows how to solve this problem? Thx.

[wkh237]

@MQZhangThu , thanks for reporting the issue 👍 looks like it's related to square/okhttp#2190, there's already a PR(#86) to solve this issue, but I don't have time to test and merge it, I'll update the status in this thread once it got merged.

[wkh237]

After some test, I found that when simply overrides contentLength() can disable the chunk encoding. However, the given content length should be correct otherwise it will lead to an unexpected end of stream error.

[MQZhangThu]

👍 so what is the recommend way to set the content length? One possible way is seting the "content-length" header as the byte number when calling RNFetchBlob.fetch? However, this may be a little weird, as in my opinion, the "content-length" should be set by RNFetchBlob lib itself, not by the user. :)

[wkh237]

Yeah, but I can't calculate correct content length from multipart body so far, I think it might takes some time.

[wkh237]

@MQZhangThu , I've published 0.9.2-beta.4 to npm, the requests in Android should be fixed length request now. I wish you could try install this version and help us verify if the problem has been resolved, Thank you ! 😃

[MQZhangThu]

@wkh237 It works now. Great. But the uploadProgress seems not working well.

[wkh237]

@MQZhangThu , thank you for the information, I've fixed the bug in 0.9.2-beta.6, please install this version to repair the function.