iZONE

Header-Case

Every word capitalised and joined by hyphens - the standard format for HTTP header names. Supports up to 50,000 characters.

Programming Tools

Input Text

0 / 50,000

Converted Text

Result will appear here…
About

What is Header-Case?

Header-Case capitalises the first letter of every word and joins them with hyphens. It is the canonical format for HTTP header names as defined in RFC 7230 - Content-Type, Accept-Encoding, X-Request-Id, Authorization. While modern HTTP/2 implementations normalise headers to lowercase internally, Header-Case remains the human-readable standard used in documentation, tooling, and API design across the industry.

Example

Input

content type accept encoding

Output

Content-Type-Accept-Encoding

Usage

When to use Header-Case?

HTTP request & response headers

All standard and custom HTTP headers follow Header-Case - Content-Type, Authorization, X-Api-Key, Cache-Control, Accept-Language.

API documentation

When documenting REST APIs, header names are always written in Header-Case regardless of how the underlying transport normalises them.

Custom X- headers

Custom application headers follow the same convention - X-Request-Id, X-Correlation-Id, X-Forwarded-For, X-Rate-Limit-Remaining.

Middleware & proxy config

Nginx, Caddy, and API gateway configs reference header names in Header-Case when defining forwarding rules and access policies.