Replace references to obsolete RFC 1341 with RFC 2046

Signed-off-by: Kévin Commaille <zecakeh@tedomum.fr>
matrix-org · Jun 13, 2024 · 89d3b1e · 89d3b1e
1 parent 672af37
commit 89d3b1e
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/data/api/server-server/content_repository.yaml b/data/api/server-server/content_repository.yaml
@@ -37,7 +37,7 @@ paths:
               schema:
                 # This is a workaround for us not being able to say the response is required.
                 description: |-
-                  **Required.** MUST contain a `boundary` (per [RFC 1341](https://www.w3.org/Protocols/rfc1341/7_2_Multipart.html))
+                  **Required.** MUST contain a `boundary` (per [RFC 2046](https://datatracker.ietf.org/doc/html/rfc2046#section-5.1))
                   delineating exactly two parts:
 
                   The first part has a `Content-Type` header of `application/json`
@@ -154,7 +154,7 @@ paths:
               schema:
                 # This is a workaround for us not being able to say the response is required.
                 description: |-
-                  **Required.** MUST contain a `boundary` (per [RFC 1341](https://www.w3.org/Protocols/rfc1341/7_2_Multipart.html))
+                  **Required.** MUST contain a `boundary` (per [RFC 2046](https://datatracker.ietf.org/doc/html/rfc2046#section-5.1))
                   delineating exactly two parts:
 
                   The first part has a `Content-Type` header of `application/json`