From d028d6e35a7316d8bafc39b505b588677b1feeaf Mon Sep 17 00:00:00 2001 From: Michael Toomim Date: Sun, 3 Sep 2023 23:40:58 -0700 Subject: [PATCH] Content-Type -> Patch-Type --- draft-toomim-httpbis-braid-http-03.txt | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/draft-toomim-httpbis-braid-http-03.txt b/draft-toomim-httpbis-braid-http-03.txt index 77ffc5e..815fd25 100644 --- a/draft-toomim-httpbis-braid-http-03.txt +++ b/draft-toomim-httpbis-braid-http-03.txt @@ -315,9 +315,9 @@ Table of Contents The previous example uses the Range Patch format, which is defined in [RANGE-PATCH]. However, one can use any patch format, by sending a - patch with a Content-Type set to a patch format with a defined - behavior, such as application/json-patch+json (as specified in - [RFC6902]): + patch with a Patch-Type set to a content-type with a defined behavior + for the HTTP PATCH method, such as application/json-patch+json (as + specified in [RFC6902]): Request: @@ -331,7 +331,7 @@ Table of Contents Patches: 1 | | Content-Length: 326 | | Patch - Content-Type: application/json-patch+json | | + Patch-Type: application/json-patch+json | | | | [ | | { "op": "test", "path": "/a/b/c", "value": "foo" }, | | @@ -347,7 +347,7 @@ Table of Contents HTTP/1.1 200 OK Patches: OK - Every patch MUST include either a Content-Type or a Content-Range. + Every patch MUST include either a Patch-Type or a Content-Range. 2.4. GET a specific version @@ -481,7 +481,7 @@ Table of Contents Patches: 1 | | Content-Length: 326 | | Patch - Content-Type: application/json-patch+json | | + Patch-Type: application/json-patch+json | | | | [ | | { "op": "test", "path": "/a/b/c", "value": "foo" }, | |