Replies: 1 comment
-
This ended up working for us, I submitted a PR to also contribute the fix upstream: #2606 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Acknowledgements
go get -u github.com/aws/aws-sdk-go-v2/...
)Describe the bug
while using the sigv4a library (based on 9805a19) we were getting
"IncompleteSignatureException: 'connection' is named as a SignedHeader, but it does not exist in the HTTP request."
despite connection header being part of the http request.Expected Behavior
for the signature to be accepted. I'm also curious why excluding the connection header as part of the signature seems to work?
Current Behavior
"IncompleteSignatureException: 'connection' is named as a SignedHeader, but it does not exist in the HTTP request."
Reproduction Steps
as per this example connection is part of SignedHeaders and is part of the http request
Possible Solution
I noticed in the java sdk, connection is added as an ignored header https://github.com/aws/aws-sdk-java-v2/blob/dc695de6ab49ad03934e1b02e7263abbd2354be0/core/auth/src/main/java/software/amazon/awssdk/auth/signer/internal/AbstractAws4Signer.java#L59 adding it to this list
aws-sdk-go-v2/aws/signer/internal/v4/headers.go
Line 7 in 50d16cf
Additional Information/Context
No response
AWS Go SDK V2 Module Versions Used
we're using an internal copy of 9805a19 where the sigv4a library is not in an internal package
Compiler and Version used
go 1.21.5
Operating System and version
Oracle Linux 8
Beta Was this translation helpful? Give feedback.
All reactions