@dkocher commented

Some [source:trunk/source/ch/cyberduck/core/ec work] has been done to support [Eucalyptus http://eucalyptus.cs.ucsb.edu/] already. I tested against the [public installation http://eucalyptus.cs.ucsb.edu/wiki/EucalyptusPublicCloud] where uploads fail and therefore it is not currently enabled yet.

@dkocher commented

The actual Walrus error message is Could not identify the operation component of the request when issueing a HEAD request on a bucket.

@dkocher commented

Replying to [3125 ringods]:

I know of a number of cloud companies that are making a replica of the S3 API for their own cloud. To be able to use Cyberduck as the client tool to access the files, I would like the S3 URL field to be editable when I create an S3 account. This way, I can use Cyberduck beyond the real Amazon S3.

Do they use other implementations than Eucalyptus?

5cfbca2 commented

Replying to [comment:4 dkocher]:

Do they use other implementations than Eucalyptus?

Yes, they have a complete implementation of their own (closed source). Is there a Cyberduck build somewhere that I can use to test against their implementation?

@dkocher commented

Replying to [comment:5 ringods]:

Replying to [comment:4 dkocher]:

Do they use other implementations than Eucalyptus?

Yes, they have a complete implementation of their own (closed source). Is there a Cyberduck build somewhere that I can use to test against their implementation?

You have to build from source and enable and add Protocol.EUCALYPTUS to the list of known protocols in [source:trunk/source/ch/cyberduck/core/Protocol.java#L487]. This protocol then selectable from the popup in the bookmark dialog will allow you to change the hostname. It is configured not to use DNS bucket names and allows to set an endpoint other than / in [source:trunk/source/ch/cyberduck/core/ec/ECSession.java#L62].

@dkocher commented

In 3f53c22.