-
-
Notifications
You must be signed in to change notification settings - Fork 902
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
Signature mismatch with s3 path style requests for signature v4 when using endpoint host like a http://<host:port/some_path> #1366
Comments
DEBUG: Canonical Request: As you see host is localhost:8080/s3. But it should be localhost:8080. Because in http, a host can't be like localhost:8080/s3 |
Which s3 compatible service or software stack are you using? Because it is a case where it is complicated to know what should be the correct behavior:
|
@artashesbalabekyan Would you be able to give more details about the service that you are using to be encountering this situation? |
For example I want use a http://localhost:8080/s3 as an endpoint. And in this case s3cmd calculates the v4 signature wrong.
It should use the hostname http://localhost:8080 not the http://localhost:8080/s3 for signature calculation.
Any ideas about it? How it can be solved?
The text was updated successfully, but these errors were encountered: