-
Notifications
You must be signed in to change notification settings - Fork 248
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
Provide sigv4 apply_to_request_http1x function #1041
Comments
yeah I can add this this morning. Can you remind me of your use cases for needing to sign requests directly? |
Amazon Managed Prometheus. |
## Motivation and Context - awslabs/aws-sdk-rust#1041 ## Description Enable signing Http 1x requests. ## Testing Unit tests ## Checklist <!--- If a checkbox below is not applicable, then please DELETE it rather than leaving it unchecked --> - [ ] I have updated `CHANGELOG.next.toml` if I made changes to the smithy-rs codegen or runtime crates - [ ] I have updated `CHANGELOG.next.toml` if I made changes to the AWS SDK, generated SDK code, or SDK runtime crates ---- _By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice._
Comments on closed issues are hard for our team to see. |
Describe the feature
Please provide a version of https://docs.rs/aws-sigv4/latest/aws_sigv4/http_request/struct.SigningInstructions.html#method.apply_to_request_http0x against the http 1.x crate.
I would do this PR myself and submit but I'm a little hazy on how you all want to handle the features that gate 0.x and 1.x moving forward in the future. Thank you!
Use Case
Need to call this function with http 1.0 requests. For now I just copied the function but it would be nice to have it included.
Proposed Solution
No response
Other Information
No response
Acknowledgements
A note for the community
Community Note
The text was updated successfully, but these errors were encountered: