-
Notifications
You must be signed in to change notification settings - Fork 1.1k
GetObject with range cause SignatureDoesNotMatch #366
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
Comments
The problem is due to setting Schem as HTTP by mistake. The interesting point is it worked well without "range:bytes=....". |
Does anyone know why this can't work with HTTP and how to work around it? I'm trying to do a threaded multi-part download through an HTTP proxy using |
As I tried, you can only use HTTPS. |
I've confirmed that HTTPS does make the error go away, but the odd thing with that is that I don't see the failed signature check with HTTP if I'm in a setup where I don't need my proxy. I have yet to test this with the latest build so I don't know if how the new |
Uh oh!
There was an error while loading. Please reload this page.
With the following code, getObjectOutcome reports SignatureDoesNotMatch. If the WithRange is comment out, everything is fine.
The corresponding logs are attached.
aws_sdk_2016-12-06-15-without-range.log.txt
aws_sdk_2016-12-06-15-with-range.log.txt
The text was updated successfully, but these errors were encountered: