cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Min Chen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-3341) Object_Store_Refactor - "Download Template" Link gets a 403 from object store.
Date Thu, 04 Jul 2013 00:55:22 GMT

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

Min Chen commented on CLOUDSTACK-3341:
--------------------------------------

By examining further what returned from extractTemplateCmd api, I realized that the URL returned
from API is different from what is displayed from
pop-up dialog from UI. Directly using the link returned from API (with / encoded as %2F can
successfully download the template. So the issue here is that UI decoded the URL string returned
from API in displaying in the browser. Jessica, can you take a look at this?
                
> Object_Store_Refactor - "Download Template" Link gets a 403 from object store.
> ------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3341
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3341
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.2.0
>         Environment: chrome on linux
> devcloud
> Cloudian or Amazon AWS S3 object stores (you'll need an S3 account on either)
>            Reporter: Thomas O'Dowd
>            Assignee: Min Chen
>            Priority: Critical
>              Labels: s3
>         Attachments: pop-up_download_link.png
>
>
> 1. Login to a freshly deployed devcloud server.
> 2. Click Infrastructure
> 3. Click secondary Storage
> 4. Remove NFS
> 5. Add new S3 Secondary Storage (without https so the S3 traffic is easy to sniff).
>    (I used AWS with 300,000 timeouts (just to be sure as s3 errors are not shown))
>    (I used a pre-allocated bucket (as is expected)).
> 6. Click on Templates
> 7. Register a new template - I used a copy of the tinylinux.vhd image that comes with
devcloud but I uploaded it under a new name - MyTiny.
> 8. use s3cmd or other external tool and wait until the template is in the directory.
This can take time as it is uploaded using multipart uploads which are not visible in the
bucket until the upload is complete.
> 9. Once available, click again on Templates.
> 10. Hover over the QuickView of the MyTiny template.
> 11. Click "Download Template"
> 12. Confirm you want to download and a pop-up will appear asking you to click a large
link.
> 13. Click the large link (this is ugly but less important than the actual issue).
> Expectation:
> 14. The template will be downloaded by your browser.
> Actual:
> 14. An XML error indicating a signature failure and no template downloaded.
> I have replicated this issue on both Amazon S3 and Cloudian S3 Object Stores.
> I will add more details to this issue shortly.

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

Mime
View raw message