Mailing-List: contact callback-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: callback-dev@incubator.apache.org
Date: Tue, 19 Jun 2012 16:53:43 +0000 (UTC)
From: "Filip Maj (JIRA)" <jira@apache.org>
To: callback-dev@incubator.apache.org
Message-ID: <1117235810.30514.1340124823279.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <1191088947.12853.1339599222898.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Assigned] (CB-912) FileTransfer.download does not fire
 error callback when server is unavailable
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Filip Maj reassigned CB-912:
----------------------------

    Assignee: Filip Maj
    
> FileTransfer.download does not fire error callback when server is unavailable
> -----------------------------------------------------------------------------
>
>                 Key: CB-912
>                 URL: https://issues.apache.org/jira/browse/CB-912
>             Project: Apache Cordova
>          Issue Type: Bug
>    Affects Versions: 1.8.0
>         Environment: Android/iOS
> Others untested
>            Reporter: Dewang Shah
>            Assignee: Filip Maj
>         Attachments: cb-915-repro.tar.gz
>
>
> The download method on FileTransfer never fires the error callback if there is a network connection but the download URL is not accessible. It simply waits forever and does not return.
> Reproduction:
>         var fileTransfer = new FileTransfer();
>         fileTransfer.download('http://nosuchserver/nosuchfile.png', fullPath, function(entry) {
>             console.log("download complete: " + entry.fullPath);
>         }, function(error) {
>             console.log("download error source " + error.source);
>             console.log("download error target " + error.target);
>             console.log("download error code" + error.code);
>         });

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira