Skip to content

Nitpick content-encoding. See #1100 #1150

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Nov 19, 2021
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion jsonschema-validation.xml
Original file line number Diff line number Diff line change
Expand Up @@ -975,7 +975,8 @@
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.
</t>
<t>
As "base64" is defined in both RFCs, the definition
Expand Down