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

swift uses incorrect port for http. #6798

Closed
cyberduck opened this issue Aug 6, 2012 · 2 comments
Closed

swift uses incorrect port for http. #6798

cyberduck opened this issue Aug 6, 2012 · 2 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Aug 6, 2012

Koert Xls created the issue

I have a setup in which the authentication server uses https, and the object gateways use http. Cyberduck tries to connect to the object gateway on port 443, even though it should be using port 80.

Transcript (I removed the irrelevant headers)
CONNECTION 1: https://authenticationhost:443

GET /v1.0 HTTP/1.1
x-auth-user: USERNAME
x-auth-key: PASSWORD
Host: authenticationhost:443

HTTP/1.1 204 No Content
X-Storage-Url: http://proxyhost/v1/AUTH_TENANT
X-Auth-Token: fbbcb5d7f18541d9963ceaa180ac4dc3

CONNECTION 2: https://proxyhost:443

GET /v1/AUTH_TENANT?limit=10000&format=xml HTTP/1.1
X-Auth-Token: fbbcb5d7f18541d9963ceaa180ac4dc3
Host: proxyhost

As you can see, the connection goes to the wrong port, and though the server is listening there, it doesn't understand the request, because CyberDuck doesn't make a valid ssl connection.

If the authentication server returns the port number in the url, thing go as expected, and cyberduck happilly connects to the specified port.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Aug 6, 2012

Koert Xls commented

This issue is similar to, but different from #6570.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Oct 5, 2012

@dkocher commented

Can you confirm this is fixed in the latest snapshot build available.

Loading

@cyberduck cyberduck closed this Oct 5, 2012
@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