Re: Registering Content-MD5

• From: Roy T. Fielding <fielding@gbiv.com>
• Date: Wed, 10 Oct 2018 17:18:59 -0700
• To: Mark Nottingham <mnot@mnot.net>
• Cc: HTTP Working Group <ietf-http-wg@w3.org>
• Message-Id: <D3146782-C8AD-4755-96AB-9273C1825787@gbiv.com>

> On Oct 10, 2018, at 4:06 PM, Mark Nottingham <mnot@mnot.net> wrote:
> 
> In <https://github.com/httpwg/http-core/issues/93>, we noticed that while RFC7231 talks about deprecating the Content-MD5 header, the change didn't make its way into the registry, causing some amount of confusion.
> 
> Is there any objection in the working group to asking IANA* to update the Permanent Message Header registry with:
> 
> Header name: Content-MD5
> Protocol: http
> Status: obsoleted
> Reference: RFC7231, Appendix B

Hmm, I think it should be

   Reference: RFC2616 (obsoleted by RFC7231)

to be consistent with the Status.

+1

....Roy

Received on Thursday, 11 October 2018 00:19:27 UTC