--- layout: default ---

Range

IANA permanent request RFC 9110 2 spellings

Declared by 36 providers across 156 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.

Rangerange

The registry

Status	permanent
Reference	RFC 9110, Section 14.2: HTTP Semantics

Providers declaring it (36)

amazon-healthomics amazon-s3 armor artifactory autodesk autodesk-fusion aws-s3 brewpage cloudflare-r2 cubefs engineering-platform etsi filebase heroku hugging-face-transformers infobip instabase kiteworks lakefs microsoft-azure microsoft-azure-blob-storage nhost oracle peertube rook sentinel-hub supabase the-climate-corporation tigris-data toornament upwind upwind-security wikimedia wikipedia xquik-api zot

Explore

All headers Representation Metadata Guidance on headers.apievangelist.com