cordova-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rajat Paharia (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CB-7901) Upload times out and fails with 400 error sometimes - Android
Date Wed, 29 Oct 2014 22:34:33 GMT

     [ https://issues.apache.org/jira/browse/CB-7901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rajat Paharia updated CB-7901:
------------------------------
    Attachment: failure1.txt

A failed upload. Look at the beginning and the end of the file. I've left all the stuff in
the middle so you can see how long it took.

> Upload times out and fails with 400 error sometimes - Android
> -------------------------------------------------------------
>
>                 Key: CB-7901
>                 URL: https://issues.apache.org/jira/browse/CB-7901
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: Plugin File Transfer
>    Affects Versions: 4.0.0
>         Environment: Android 4.4.4
>            Reporter: Rajat Paharia
>         Attachments: failure1.txt, failure2.txt, success1.txt, success2.txt
>
>
> Using: 
> - Cordova 4.0.0
> - org.apache.cordova.file-transfer 0.4.7 "File Transfer"
> - Android 4.4.4 (Moto X)
> I am uploading image files from my phone to AWS S3 (via https) using the File Transfer
plugin. When using Wifi, this seems to work with no issues - I have not been able to get it
to fail. I have setup a progress callback to log to the console and the "win" callback is
called almost immediately after the last progress event. 
> When using the cell network (with 1-2 out of 5 bars), on the other hand, it fails intermittently.
The progress events seem to indicate that the file is almost done uploading, then there is
a long delay, and then the fail callback is called. 
> File size doesn't have any effect. 
> I am attaching logcats of both successes and failures. The successes show a 204 response
from the AWS server shortly after the last progress event. The failures show a long delay
after the last progress event, and then a 400 response from the AWS server with the following
message "Your socket connection to the server was not read from or written to within the timeout
period. Idle connections will be closed."
> Google searching on this phrase reveals that the most common cause is the Content-Length
being set to more than the number of bytes actually sent. Given that this only happens on
slower connections, I'm not sure if that's relevant in this case. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@cordova.apache.org
For additional commands, e-mail: issues-help@cordova.apache.org


Mime
View raw message