Content-MD5
obsoleted
request
RFC 2616
2 spellings
Declared by 11 providers across 176 published specification files in the APIs.io network.
A count here is providers whose published contract declares this header — not
providers who send it. Response headers set at the edge rarely appear in an OpenAPI at all, so a low
number can measure documentation practice rather than deployment.
Spelled 2 ways
HTTP field names are case-insensitive (RFC 9110 §5.1), so every spelling below is the same header on the wire. A contract is not the wire: generated clients key off the string, and a developer reading two of these sees two different headers.
Content-MD5content-md5
The registry
| Status | obsoleted |
|---|---|
| Reference | RFC 2616, Section 14.15: Hypertext Transfer Protocol -- HTTP/1.1 |
Providers declaring it (11)
amazon-s3 aws-s3 box cloudflare-r2 cubefs engineering-platform lawvu microsoft-azure oracle va va-gov
Explore
All headers Representation Metadata Guidance on headers.apievangelist.com