From 158ec6ead4216cf6d9caecabff7edcfd605303d5 Mon Sep 17 00:00:00 2001 From: Gaspard Wierzbinski Date: Sun, 17 Dec 2023 00:05:14 -1000 Subject: [PATCH] Update spec.md --- docs/spec.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/spec.md b/docs/spec.md index b046b40..c3c8429 100644 --- a/docs/spec.md +++ b/docs/spec.md @@ -16,7 +16,7 @@ Lysand-compatible servers may implement other protocols as well, such as Activit # Required Across Implementations -All HTTP request bodies and response bodies **MUST** be encoded as UTF-8 JSON, with the `Content-Type` header set to `application/json; charset=utf-8`. If cryptography is supported by the server, there **MUST** also be a `Signature` header as defined in [/signatures](the signatures spec). +All HTTP request bodies and response bodies **MUST** be encoded as UTF-8 JSON, with the `Content-Type` header set to `application/json; charset=utf-8`. If cryptography is supported by the server, there **MUST** also be a `Signature` header as defined in [the signatures spec](/cryptography/signing). Servers **MUST** use UUIDs or a UUID-compatible system for the `id` field. Any kind of UUID is allowed, as long as it is a valid UUID. It **should** be unique across the entire known network if possible, but this is not needed as long as the server can guarantee that the `id` is unique across the server. @@ -24,4 +24,4 @@ Servers **MUST** use UUIDs or a UUID-compatible system for the `id` field. Any k All URIs **MUST** be absolute URIs, and **MUST** be HTTPS URIs, except for development purposes. They **MUST** be unique across the entire network, and **MUST** contain the `id` of the object in the URI. They **should not** contain data that can be changed, such as the actor's `username`. -All URIs **MUST** be normalized, and **MUST NOT** contain any query parameters \ No newline at end of file +All URIs **MUST** be normalized, and **MUST NOT** contain any query parameters