-
-
Notifications
You must be signed in to change notification settings - Fork 903
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
Specifying a custom port in host_base cases V4 signature error #974
Comments
Aws signature documentation states that the "port" should not be included for the host field used for signature if it is standard ports 80 for http and 443 for https. Sadly, there no way to test with amazon that if we were to use another port, the port info would be needed. I might add in the signature a directive like: if port = 80 or 443 then "strip it". |
Actually, this is what Boto team did. As well AWS cli: |
Hum, I need to check but I think that I already fixed the issue already.
Le mar. 31 juil. 2018 18:13, samuelsh <notifications@github.com> a écrit :
… Actually, this is what boto team did.
The stripping standard port from host header:
boto/botocore#1296 <boto/botocore#1296>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#974 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABAUpFVMdUizQqEOz05mXr_2WylPJm70ks5uMIIogaJpZM4UHiKs>
.
|
No, I just verified the problem still exists in 2.0.2 and in latest source. Removing
|
@jamshid : In fact the issue was not to set a port, but when it was set exactly to ":80" or ":443" (depending of your ssl setting). Don't hesitate to re-open / tell me if you still have issues with the last fixes. |
fixed? |
I test s3cmd against an S3-compatible service and sometimes the test system's S3 endpoint uses a port that is not the default 80 or 443.
Since I configure ~/.s3cfg with a script during testing I usually included the port number in host_base / host_bucket, even if it is the default, e.g.
I just discovered that only works as long as you're using
signature_v2=True
. If you comment that out and use V4 signatures then s3cmd fails with a 403 SignatureDoesNotMatch.Is the problem related to the Host header? Is there another way that the port number should be specified?
The text was updated successfully, but these errors were encountered: