Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Date: Fri, 26 Oct 2012 02:07:12 +0000 (UTC)
From: "Simon MacDonald (JIRA)" <jira@apache.org>
To: callback-dev@incubator.apache.org
Message-ID: <1309056361.30457.1351217232705.JavaMail.jiratomcat@arcas>
In-Reply-To: 
 <770590677.17327.1334240116768.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (CB-488) FileTransfer.upload does not follow
 redirects on Android
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CB-488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13484650#comment-13484650 ] 

Simon MacDonald commented on CB-488:
------------------------------------

I parked it due to the talk about super-ceding FileTransfer with XHR2. 
                
> FileTransfer.upload does not follow redirects on Android
> --------------------------------------------------------
>
>                 Key: CB-488
>                 URL: https://issues.apache.org/jira/browse/CB-488
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: Android
>    Affects Versions: 1.3.0, 1.4.0, 1.5.0
>         Environment: Andoid device: Samsung Galaxy S Plus
>            Reporter: Wouter
>            Assignee: Simon MacDonald
>             Fix For: Master
>
>
> We are trying to upload a local move file to Youtube though the Youtube API. This API works in such a way that after uploading a file a redirect is done to another location. Unfortunately the Android implementation of FileTransfer does not follow this redirect. (The iPhone implementation does follow the redirect.)
> Steps to reproduce:
> - Create a FileTransfer instance and call the upload method following the example at http://docs.phonegap.com/en/1.6.0/cordova_file_file.md.html#FileTransfer
> - The server the file is posted to (in the sample this is http://some.server.com/upload.php) should do a redirect to another location to reproduce this issue.
> Actual Result:
> - In the success callback the FileUploadResult.responseCode is 302, and the FileUploadResult.response is "Temporarily Moved" (or similar depending on the webserver that responded with the redirect).
> Expected Result:
> - The redirect is followed and the result of the new location is retreived and represented in the FileUploadResult instance.
> Or (but lower preference):
> - The FileUploadResult instance also contains the HTTP headers that were sent with the response so that the Location header (containging the url to redirect to) is known.

--
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