feat: Add rate limiting

This commit is contained in:
Jesse Wierzbinski 2024-10-18 11:19:02 +02:00
parent 7704d5e0ab
commit e69ef9c989
No known key found for this signature in database
2 changed files with 11 additions and 0 deletions

View file

@ -17,6 +17,7 @@ This page lists changes since Working Draft 3. {{ className: 'lead' }}
- `X-Signed-By` to `Versia-Signed-By`
- Removed the nonce from the [signature system](/signatures), replaced with `Versia-Signed-At` (timestamps).
- Added `html_uri` to [Notes](/entities/note).
- Standardize rate limits with [IETF draft draft-polli-ratelimit-headers-02](https://www.ietf.org/archive/id/draft-polli-ratelimit-headers-02.html).
## Since WD 3

View file

@ -47,6 +47,16 @@ ALL kinds of HTTP requests/responses between instances **MUST** include a [Signa
</Col>
</Row>
## Rate limits
Implementations **MUST** respect the rate limits of remote instances.
IETF draft [draft-polli-ratelimit-headers-02](https://www.ietf.org/archive/id/draft-polli-ratelimit-headers-02.html) **MUST** be used to communicate rate limits. Other rate limit headers/formats are not allowed.
<Note>
This IETF draft is, well, a draft. However, there are no standards for rate limiting in HTTP, so this is the best we have.
</Note>
## Responses
<Row>