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
panic: runtime error: slice bounds out of range [3:1] in GetURIPath
#1294
Comments
Thanks @Juneezee, indeed setting the protocol fixes this weird panic. |
Just hit this panic too |
Thanks for the update @alexrudd. Do you have any details available how you were able to reproduce this issue? In addition could you include the version of the SDK that you are using? |
This issue has not received a response in 1 week. If you want to keep this issue open, please just leave a comment below and auto-close will be canceled. |
comment edited since out of topic |
I ran into this too with SDK v1.16.5. @jasdel the code provided by @Juneezee looks about right:
But in my case I used dynamodb |
Fixes aws#1294 by correcting how GetURIPath parses the Opaque field of a url.URL value. Adds test cases for GetURIPath to validate its behavior.
Fixes aws#1294 by correcting how GetURIPath parses the Opaque field of a url.URL value. Adds test cases for GetURIPath to validate its behavior.
Thanks for updating this issue. I've put out PR #1754 that corrects how the SDK's signer is handling opaque URL paths. The PR also added several tests that should prevent this kind of issue in the future. |
Fixes aws#1294 by correcting how GetURIPath parses the Opaque field of a url.URL value. Adds test cases for GetURIPath to validate its behavior.
) Fixes #1294 by correcting how GetURIPath parses the Opaque field of a url.URL value. Adds test cases for GetURIPath to validate its behavior.
|
Describe the bug
I am using Minio for local development with S3. If I specific an endpoint
URL
withouthttp://
, it panics.Output when I run the program
Version of AWS SDK for Go?
v1.6.0
Version of Go (
go version
)?To Reproduce (observed behavior)
Expected behavior
config.LoadDefaultConfig
should return an error ifURL
must be prefixed with a scheme. Otherwise, I expect the endpoint resolver to be able to useURL
without a scheme.Additional context
N/A
The text was updated successfully, but these errors were encountered: