From e92923303519e54856450fbbddb9264be0d23d71 Mon Sep 17 00:00:00 2001 From: Roberto Polli Date: Mon, 15 Nov 2021 15:19:33 +0100 Subject: [PATCH 1/2] Nitpick content-encoding. See #1100 --- jsonschema-validation.xml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/jsonschema-validation.xml b/jsonschema-validation.xml index fb244a0a..9d61f568 100644 --- a/jsonschema-validation.xml +++ b/jsonschema-validation.xml @@ -975,7 +975,9 @@ encodings used in MIME. This keyword is derived from MIME's Content-Transfer-Encoding header, which was designed to map binary data into ASCII characters. It is not related to HTTP's Content-Encoding header, - which is used for compressing HTTP request and response payloads. + which is used to encode (e.g. compress or encrypt) + the content of HTTP request and responses. + As "base64" is defined in both RFCs, the definition From 5f86044878b0532abd74a4da2f891b7be3386aa5 Mon Sep 17 00:00:00 2001 From: Roberto Polli Date: Mon, 15 Nov 2021 15:21:41 +0100 Subject: [PATCH 2/2] Update jsonschema-validation.xml --- jsonschema-validation.xml | 1 - 1 file changed, 1 deletion(-) diff --git a/jsonschema-validation.xml b/jsonschema-validation.xml index 9d61f568..9abdc1de 100644 --- a/jsonschema-validation.xml +++ b/jsonschema-validation.xml @@ -977,7 +977,6 @@ into ASCII characters. It is not related to HTTP's Content-Encoding header, which is used to encode (e.g. compress or encrypt) the content of HTTP request and responses. - As "base64" is defined in both RFCs, the definition