You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The same thing is true for all the URLs when a file under a bucket is selected. Here's an example of the basic one:
Invalid Cyberduck URL: ecc.eucalyptus.com/chimpeenuts-bucket/Argentina.gif
What the URL should be: ecc.eucalyptus.com:8773/services/Walrus/chimpeenuts-bucket/Argentina.gif
We make the assumptions that as in AWS S3, a file is also available over the HTTP default port for anonymous users (if the ACL allows this) and therefore always add this URL for the HTTP URL. We should possibly add the original URL with the port the browser is connected to as well (443 in case of AWS, custom port for Eucalyptus installations).
Auto-generated URLs do not correctly use Walrus endpoint and port #.
To re-create:
The URL generated does not include the port # or the /services/Walrus endpoint.
ecc.eucalyptus.com/chimpeenuts-bucket
ecc.eucalyptus.com:8773/services/Walrus/chimpeenuts-bucket
The same thing is true for all the URLs when a file under a bucket is selected. Here's an example of the basic one:
Invalid Cyberduck URL: ecc.eucalyptus.com/chimpeenuts-bucket/Argentina.gif
What the URL should be: ecc.eucalyptus.com:8773/services/Walrus/chimpeenuts-bucket/Argentina.gif
See attached screenshots.
Attachments
Screen shot 2011-09-08 at 8.49.34 AM.png
(7.5 KiB)Screen shot 2011-09-08 at 8.56.25 AM.png
(54.0 KiB)The text was updated successfully, but these errors were encountered: