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

Not using proper storage url when connecting to swift #5216

Closed
cyberduck opened this issue Sep 20, 2010 · 4 comments
Closed

Not using proper storage url when connecting to swift #5216

cyberduck opened this issue Sep 20, 2010 · 4 comments
Assignees
Milestone

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Sep 20, 2010

drue created the issue

Attempting to connect to a Swift install. Cyberduck appears to authenticate using https on a nonstandard port but subsequent ssl requests are going to the auth URL instead of the storage URL returned with the authentication request. Cyberduck doesn't report an error until you try to create a folder or upload some files.

i.e. auth url = https://x.x.x.x:11000/v1.0 and the returned storage url is https://x.x.x.x:443/v1 but after authentication the subsequent requests from Cyberduck go to port 11000 instead of 443.

note that python-cloudfiles and Fog seem are working as expected with this Swift installation.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Sep 27, 2010

@dkocher commented

In 51dcf83. Please test with the latest snapshot build available.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Sep 27, 2010

drue commented

build 7089 seems to be attempting to authenticate to port 443 despite putting a different port into the port box

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Sep 27, 2010

@dkocher commented

Replying to [comment:4 drue]:

build 7089 seems to be attempting to authenticate to port 443 despite putting a different port into the port box

Thanks for testing. I don't have an openstack installation therefore the different result. Fix should now be in cdeac7e.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Sep 28, 2010

drue commented

seems to be working, thank you!

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

No branches or pull requests

2 participants