[
https://issues.apache.org/jira/browse/CB-2423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13577811#comment-13577811
]
Andrew Grieve commented on CB-2423:
-----------------------------------
Might not be as simple as it sounds.
- Some servers reject requests that set the content-length when using chunked
mode.
- Not using chunked mode for https can cause out-of-memory exceptions.
You could try setting chunkedMode to false, which should set the content-length
header via setFixedLengthStreamingMode()
Moving to OkHttp might be the best way to resolve all of these FileTransfer
woes.
> FileTransfer does not set Content-Length header even if known -- unable to
> upload to Amazon
> -------------------------------------------------------------------------------------------
>
> Key: CB-2423
> URL: https://issues.apache.org/jira/browse/CB-2423
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
> Affects Versions: 2.4.0
> Environment: Android client
> Reporter: Thomas O'Dell
> Assignee: Joe Bowser
> Labels: features
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> FileTransfer does not set the Content-Length header even when known, which
> causes Amazon S3 to return HTML Code 411 (Length Required).
> Adding the following lines after line 328 solves the problem:
> if (fixedLength >= 0) {
> conn.setRequestProperty("Content-Length", ""+fixedLength);
> }
> (Haven't tested on iOS, but see that iOS does have code to set
> Content-Length.)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
