-
Notifications
You must be signed in to change notification settings - Fork 183
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
[BUG] Bug with AWS
if id
has special characters
#833
Comments
Do other requests against an AWS instance work, aka if the ID doesn't have a special character in it? Let's narrow it down.
|
I'm seeing the same bug happen, only when using |
@fabiopedrosa thanks a lot for the comment, could not find a time for the asked code. So when "AsyncHttpConnection" is not used everything's good? |
I narrowed down the bug to this line in
|
I've created a PR for this issue to be fixed |
[Catch All Triage - 1, 2] |
@nathaliellenaa want to take this? |
Sure, I can take this one! |
I merged a fix for this in #848, thanks @nathaliellenaa. |
@Danipulok @fabiopedrosa if you have a moment, give that fix a try? |
What is the bug?
AWS + special characters in 'id' result in:
How can one reproduce the bug?
What is the expected behavior?
When using localhost openseach run via docker everything's okay. So I guess there's a problem with
AWSV4SignerAsyncAuth
somewhereWhat is your host/environment?
Win10
Python 3.12.3
opensearch-py==2.7.0
boto3==1.35.2
Do you have any additional context?
Maybe it's a bug in
boto3.Session
? If yes, please tell me, I will open the issue there.And I consider this as an issue at all since with non-aws and localhost everything's okay.
With all other ID like "foo" everything's okay with the same code, so it's not a credentials problem
The text was updated successfully, but these errors were encountered: