-
-
Notifications
You must be signed in to change notification settings - Fork 299
Interoperability with path-style requests #10956
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Is this instance publicly reachable over the Internet to reproduce the issue? |
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: Hostname would be something like: But if you need me to do anything / send any error messages, that would help you to identify the issue, |
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! |
You can disable the use of virtual host style requests by setting the preference
|
In 6ea9384. You will have to define a custom profile to disable the use of virtual host style requests. See 3e93ed4 for a sample. |
We have no made available a preconfigured connection profile. |
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.
The text was updated successfully, but these errors were encountered: