You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to make authenticated requests to AWS API endpoins and GraphQL APIs with Hurl.
This is not possible with Hurl today, as it requires a custom Authorization request header with a cryptographic signature over several parts of the request (see AWS SigV4).
Proposal
Curl has built-in support for this, so it's basically a matter of adding an aws-sigv4 option (command line and per-request) to Hurl and passing it through to Curl.
The required authentication data (secret key to generate the signature with) is passed via the --user flag (same as in Curl).
Additional context and resources
In a "classic me", I have already patched Hurl to implement this – before reading CONTRIBUTING.md.
The patch is rather simple and does work as expected: it successfully makes signed requests against AWS API endpoints. Two small issues cropped up, one if which might be a bug in Curl's SigV4 implementation.
Before I take the time to dig deeper into those issues and create a PR, I'd like to await your feedback on the proposal, as suggested by CONTRIBUTING.md.
The text was updated successfully, but these errors were encountered:
Problem to solve
I'd like to make authenticated requests to AWS API endpoins and GraphQL APIs with Hurl.
This is not possible with Hurl today, as it requires a custom Authorization request header with a cryptographic signature over several parts of the request (see AWS SigV4).
Proposal
Curl has built-in support for this, so it's basically a matter of adding an
aws-sigv4
option (command line and per-request) to Hurl and passing it through to Curl.An example Hurlfile might look like this:
The required authentication data (secret key to generate the signature with) is passed via the
--user
flag (same as in Curl).Additional context and resources
In a "classic me", I have already patched Hurl to implement this – before reading CONTRIBUTING.md.
The patch is rather simple and does work as expected: it successfully makes signed requests against AWS API endpoints. Two small issues cropped up, one if which might be a bug in Curl's SigV4 implementation.
Before I take the time to dig deeper into those issues and create a PR, I'd like to await your feedback on the proposal, as suggested by CONTRIBUTING.md.
The text was updated successfully, but these errors were encountered: