httpsig
httpsig copied to clipboard
jbowes
HTTP Request Signing with ✨ STANDARDS ✨
* Adding @request-target support * Making Signature-Input parameters ordered * Making Signer interface public so it can be used by clients too * Signature-input fields can have `=` in their...
Hello, Trying out the library I looked at the example in the README and came up with this as a basic example for using a POST request: ``` package main...
Bumps [actions/checkout](https://github.com/actions/checkout) from 3.5.3 to 4.1.1. Release notes Sourced from actions/checkout's releases. v4.1.1 What's Changed Update CODEOWNERS to Launch team by @joshmgross in actions/checkout#1510 Correct link to GitHub Docs by...
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot] avatar"){kind=avatar}
The following PR implements eddsa-ed25519-sha256 signing and verifying
NewSignTransport() begins by cloning a request so it works on a copy of the original request but when reading the body into a bytes buffer, the cursor from both requests...
Current transport/middleware design works well with native Go HTTP libraries. However, if I want to use some modern HTTP libraries like gin-gonic or resty, the user experience becomes a disaster....
Currently the verifier uses a self-constructed "@signature-params" when verifying the signature. However, the order of signature params is not strictly defined in the standard. For example, the following example is...
The changelog for [draft-ietf-httpbis-digest-headers](https://datatracker.ietf.org/doc/draft-ietf-httpbis-digest-headers/) states: ``` Since draft-ietf-httpbis-digest-headers-07 * Introduced Repr-Digest and Want-Repr-Digest, and deprecated Digest and Want-Digest. Use of Structured Fields. #1993, #1919 ... Since draft-ietf-httpbis-digest-headers-05 ... * Add...
hellow @jbowes, For my own uses, I have experimented with a change which I'd like to know if you're interested in before I spend more time on it for a...
