--- layout: default ---

Content-Disposition

IANA permanent response RFC 6266 2 spellings

Declared by 96 providers across 1301 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-Dispositioncontent-disposition

The registry

Status	permanent
Reference	RFC 6266: Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)

Providers declaring it (96)

8x8 amazon-s3 api-snap appdirect argyle argyle-financial atlassian autodesk-fusion aws-s3 banqu binarly bitbucket bitbucket-pipelines bloomreach box bridge chili-piper cint cisco-webex cloudflare cloudflare-r2 convertapi conxai didit digital-ocean docker-hub dsv dust-tt earnipay ebay engineering-platform factset getaccept gladly greynoise heyform hopper-com hugging-face-transformers infobip kubeshop kuehne-nagel lalal-ai landmark-information lawvu limitless-ai logikio loop lorum mediamath meow method-financial methodfi microcks microsoft-azure moodys-rms morningstar ncino netbird netcracker nhost oracle palo-alto-networks plex primitive pruna-ai puppet-labs qualio rentberry root runloop-ai sageox schematic slashid specterops spectro-cloud spring-framework stellar thriva top-group tradeshift uniuni university-of-amsterdam university-of-basel upguard va vcv voltair webex wikimedia wikipedia writer wso2 xflow yoobic zamzar zoho

Explore

All headers Representation Metadata Guidance on headers.apievangelist.com