Skip to Content
Platform.Ontology

HTTP header order and casing

The set and order of request headers is different for each browser and HTTP library.

Used to track youNetwork and connectionHTTPWeb browsersWhen the page loads

In one line

Can tell which browser or tool you use from the order of request headers

The set and order of request headers is different for each browser and HTTP library.

Chrome, Firefox and Safari send Accept, Accept-Language, Accept-Encoding and Sec-* headers in distinct orders; scripted clients (requests, Go, Node fetch) differ. Mismatches versus the User-Agent flag bots.

What it can and can't do

What the user does: Nothing. It happens with every page request

It can

  • Compare the order and casing of header lines with known browsers
  • Spot scripts and bots that use plain code libraries
  • Flag a browser name that does not match the headers

It cannot

  • Know your name or account from it
  • See your files or other tabs
  • Tell two people on the same browser version apart

Browser support

BrowserStatusFirst versionReleasedNote
ChromeSupported12008-12-11None
EdgeSupported792020-01-15None
FirefoxSupported12004-11-09None
SafariSupported12003-06-23None
Safari on iPhoneSupported12007-06-29None
Chrome on AndroidSupported1Not listedNone
Samsung InternetSupported5.02016-12-15None

How a site asks for it

APIServer request header parsing
How access is grantednone
What the user seesNot listed
Needs a secure context (HTTPS)No
Needs a user gestureNo
How long it lastsNot listed
How to take it backNot listed
Inside an iframeNot listed

Typical flow

  1. Read headers in received order
  2. Hash names, order and values
  3. Compare with User-Agent

Data you get

What comes back: Ordered list
Shape: string

FieldTypeUnitRangePrecision
header orderlistNone10 to 20 namesexact

Technical limits

  • Proxies and CDNs can reorder headers
  • HTTP/2 lowercases names

The story

What it is

The order of the info your browser sends to a site reveals which browser it is.

For you

You never see it. Each browser sends the same pieces in a slightly different order, like a signature. A site can tell Chrome from Firefox from a script even if the browser claims otherwise.

For makers

Bot defense vendors use header order as a quick way to catch scripts pretending to be browsers. It is also a fingerprint input, since software versions and add-ons leave marks.

Where you see it

TypeExampleApps
securityA bot defense checks if the header order matches the browser claim, and blocks scripts that fake Chrome.Cloudflare, DataDome
gamesA game login page blocks credential stuffing tools that send headers in an odd order.Roblox
shoppingA sneaker or ticket site spots scalper bots by header order before the sale begins.Ticketmaster
adsAn ad platform filters click fraud from scripts with the wrong header signature.None named
analyticsA traffic report separates real browsers from crawlers.None named
mediaA streaming site stops account sharing and scraping tools by headers.None named

Risks

  • Hard to hide
  • Can flag privacy tools

Good uses and abuse

Legitimate uses

  • Bot detection

Known abuse

  • Client identification

Scores

ScoreValueMeaning
Sensitivity2 of 5How revealing the data is
Utility4 of 5How useful it is to honest apps
Friction0 of 5How much the user has to do
Fingerprint bits3Rough identifying entropy, when known

Sources

How well checked: Based on official documentation.

On this page