Repository navigation
Interoperability with path-style requests #10956
Description
Activity
fcfe459 commented
The instance is only partly reachable from the internet, sadly.
It is an instance of DELL ECS, which besides its enterprise hardware, also has a free to use community edition:
https://github.com/EMCECS/ECS-CommunityEdition/releasesHostname would be something like:
namespace.mydomain.com
and to not get SSL-Certificate problems, hostnames can't look like
bucket.namspace.mydomain.com
as it would require a ..mydomain.com SSL-Cert.
Therefore this instance sticks to namepspace.mydomain.com/bucketBut if you need me to do anything / send any error messages, that would help you to identify the issue,
I can gladly do.c3dd456 commented
Hello. Thanks for sharing such a great tool!
Unfortunately, some environments use a wildcard DNS entry that will always succeed, preventing Cyberduck from falling-back to path-style access. Would it be possible to have a configuration setting (or similar) that disables virtual host style access completely, please?
Thanks!
@dkocher commented
You can disable the use of virtual host style requests by setting the preference
s3service.disable-dns-bucketstotrue.- Set configuration option in Cyberduck
- Set configuration option in Mountain Duck
@dkocher commented
In 6ea9384. You will have to define a custom profile to disable the use of virtual host style requests. See 3e93ed4 for a sample.
@dkocher commented
We have no made available a preconfigured connection profile.
- locked as resolved and limited conversation to collaborators
on Nov 26, 2021
Hey,
in version 7.2.0, you removed the support for path style URL generation for the S3 protocol:
"Deprecated path-style request usage for (AWS GovCloud) (#10824)"
I am using CyberDuck to connect to en enterprise S3 cluster, that still and only uses path-style.
Would there maybe be the option to bring the support back?
Would be fine for me, if this is then an additional checkbox in the connection settings to use path style.
But currently I am forced to use an old version no Cyberduck and repeatedly ask my, why they can't connect with their (newer) version of CyberDuck.
Thanks a lot.