Skip to content
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

Interoperability with path-style requests #10956

Closed
cyberduck opened this issue Jan 22, 2020 · 11 comments
Closed

Interoperability with path-style requests #10956

cyberduck opened this issue Jan 22, 2020 · 11 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Jan 22, 2020

fcfe459 created the issue

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.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jan 22, 2020

@dkocher commented

Related issue with Minio in #10888.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jan 22, 2020

@dkocher commented

Is this instance publicly reachable over the Internet to reproduce the issue?

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jan 22, 2020

@dkocher commented

We have implemented a fallback in af0c7ed if resolving the DNS name for the bucket fails.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jan 22, 2020

@dkocher commented

Also as of e5e2a97 we use path-style requests when the hostname is an IP address.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jan 27, 2020

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

Hostname 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/bucket

But if you need me to do anything / send any error messages, that would help you to identify the issue,
I can gladly do.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jun 16, 2020

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!

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Dec 11, 2020

@dkocher commented

Reopen for #11416.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Dec 11, 2020

@dkocher commented

You can disable the use of virtual host style requests by setting the preference s3service.disable-dns-buckets to true.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jan 17, 2021

@dkocher commented

#11548 closed as duplicate.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jan 18, 2021

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

Loading

@cyberduck cyberduck closed this Jan 18, 2021
@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 29, 2021

@dkocher commented

We have no made available a preconfigured connection profile.

Loading

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants