diff options
| author | 2025-03-02 13:28:38 +0100 | |
|---|---|---|
| committer | 2025-03-02 13:28:38 +0100 | |
| commit | 5d0e3d9c354906409a514b437d70f7a9db90703a (patch) | |
| tree | 725b5636b301aad97494cec730e54a701c48c66f /docs/federation/http_signatures.md | |
| parent | [chore] github.com/superseriousbusiness/activity -> codeberg.org/superserious... (diff) | |
| download | gotosocial-5d0e3d9c354906409a514b437d70f7a9db90703a.tar.xz | |
[chore] github.com/superseriousbusiness/httpsig -> codeberg.org/superseriousbusiness/httpsig (#3854)
Diffstat (limited to 'docs/federation/http_signatures.md')
| -rw-r--r-- | docs/federation/http_signatures.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/federation/http_signatures.md b/docs/federation/http_signatures.md index e28e4cb14..cd7aa3c1c 100644 --- a/docs/federation/http_signatures.md +++ b/docs/federation/http_signatures.md @@ -6,7 +6,7 @@ GoToSocial will also sign all outgoing `GET` and `POST` requests that it makes t This behavior is the equivalent of Mastodon's [AUTHORIZED_FETCH / "secure mode"](https://docs.joinmastodon.org/admin/config/#authorized_fetch). -GoToSocial uses the [superseriousbusiness/httpsig](https://github.com/superseriousbusiness/httpsig) library (forked from go-fed) for signing outgoing requests, and for parsing and validating the signatures of incoming requests. This library strictly follows the [Cavage http signature RFC](https://datatracker.ietf.org/doc/html/draft-cavage-http-signatures-12), which is the same RFC used by other implementations like Mastodon, Pixelfed, Akkoma/Pleroma, etc. (This RFC has since been superceded by the [httpbis http signature RFC](https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-message-signatures), but this is not yet widely implemented.) +GoToSocial uses the [superseriousbusiness/httpsig](https://codeberg.org/superseriousbusiness/httpsig) library (forked from go-fed) for signing outgoing requests, and for parsing and validating the signatures of incoming requests. This library strictly follows the [Cavage http signature RFC](https://datatracker.ietf.org/doc/html/draft-cavage-http-signatures-12), which is the same RFC used by other implementations like Mastodon, Pixelfed, Akkoma/Pleroma, etc. (This RFC has since been superceded by the [httpbis http signature RFC](https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-message-signatures), but this is not yet widely implemented.) ## Query Parameters |
