--- layout: default ---

Content-Encoding

IANA permanent response RFC 9110 2 spellings

Declared by 39 providers across 2548 published specification files in the APIs.io network.

What this header is for, and how to use it →

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-Encodingcontent-encoding

The registry

Status	permanent
Reference	RFC 9110, Section 8.4: HTTP Semantics

Providers declaring it (39)

amazon-s3 aws-s3 axiom-co azure-log-analytics bird bitpowr-technologies-inc cerebras-systems cloudflare-r2 datadog dow-jones engineering-platform etsi factset galileo-technologies gameanalytics honeycomb-io influxdata influxdb mastodon microsoft-azure microsoft-azure-monitor moodys-rms new-relic nuon oanda oracle palo-alto-networks salesforce sendgrid shyft stardog styra university-of-amsterdam vtex wikimedia wikipedia wise zoominfo zuora

Explore

All headers Representation Metadata Guidance on headers.apievangelist.com