fix: 📝 Clarify how hashes of GET request bodies are calculated

This commit is contained in:
Jesse Wierzbinski 2024-09-19 08:08:04 +02:00
parent ec9cb1e93a
commit ce94c87564
No known key found for this signature in database

View file

@ -38,7 +38,7 @@ Where:
- `$0` is the HTTP method (e.g. `GET`, `POST`) in lowercase. - `$0` is the HTTP method (e.g. `GET`, `POST`) in lowercase.
- `$1` is the path of the request, in standard URI format (don't forget to URL-encode it). - `$1` is the path of the request, in standard URI format (don't forget to URL-encode it).
- `$2` is the nonce, a random string generated by the client. - `$2` is the nonce, a random string generated by the client.
- `$3` is the SHA-256 hash of the request body, encoded in base64. - `$3` is the SHA-256 hash of the request body, encoded in base64. (if it's a `GET` request, this should be the hash of an empty string)
Sign this string using the user's private key. The resulting signature should be encoded in base64. Sign this string using the user's private key. The resulting signature should be encoded in base64.