The Content-MD5 HTTP header — representation metadata, RFC 2616, declared by 11 providers in the API Evangelist catalog.
Content-MD5
Representation Metadata obsoleted request 2 spellings
A reference entry. The registry facts and catalog measurements below are complete; the written guidance for this header has not been authored yet.
Content-MD5 is representation metadata — Headers describing the payload itself — its type, length, encoding, disposition, location.
The registry
Listed in the IANA HTTP Field Name Registry as marked obsoleted in the registry — it should not appear in new work. Defined in RFC 2616, Section 14.15: Hypertext Transfer Protocol – HTTP/1.1.
In the catalog
Declared by 11 providers across 176 published specification files in the API Evangelist catalog, where it appears as a request header — sent by the client.
It is spelled 2 different ways across those contracts — Content-MD5, content-md5. HTTP field names are case-insensitive (RFC 9110, §5.1), so every one of these is the same header. They are not the same string, which is why generated clients disagree about it.
Governed by these rules
Machine-enforceable governance rules from rules.apievangelist.com that apply to this header when it appears in an OpenAPI.
OpenAPI Components Headers Error error
Utilizing the headers object in the centralized OpenAPI components library helps make headers reusable across API requests and responses
Guidance: Rate Limits →OpenAPI Components Headers Info info
Utilizing the headers object in the centralized OpenAPI components library helps make headers reusable across API requests and responses
Guidance: Rate Limits →OpenAPI Headers Hyphenated Pascal Case error
HTTP headers should follow Hyphenated-Pascal-Case naming convention for consistency and readability, such as Content-Type, X-Request-Id, or Accept-Language.
Guidance: Naming →