- From: Kari Hurtta <hurtta-ietf@elmme-mailer.org>
- Date: Mon, 4 Nov 2019 08:16:18 +0200 (EET)
- To: Roberto Polli <robipolli@gmail.com>, Lucas Pardue <lucaspardue.24.7@gmail.com>
- CC: Kari Hurtta <hurtta-ietf@elmme-mailer.org>, HTTP Working Group <ietf-http-wg@w3.org>
https://tools.ietf.org/html/draft-ietf-httpbis-digest-headers-01#section-2 ---- The following examples show how representation metadata, payload transformations and method impacts on the message and payload body. Here is a gzip-compressed json object Request: PUT /entries/1234 HTTP/1.1 Content-Type: application/json Content-Encoding: gzip H4sIAItWyFwC/6tWSlSyUlAypANQqgUAREcqfG0AAAA= ---- I think that this example (and other) needs something like that: Message body is shown as base64 encoded for representation purpose. / Kari Hurtta
Received on Monday, 4 November 2019 06:16:32 UTC