cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joe Bowser (JIRA)" <>
Subject [jira] [Commented] (CB-488) FileTransfer.upload does not follow redirects on Android
Date Thu, 25 Oct 2012 21:55:12 GMT


Joe Bowser commented on CB-488:

What's the status of this issue?  It doesn't look like it's been touched in months.
> FileTransfer.upload does not follow redirects on Android
> --------------------------------------------------------
>                 Key: CB-488
>                 URL:
>             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
> - The server the file is posted to (in the sample this is
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:

View raw message