Build and parse Accept headers with q values, and see the order a server resolves them in — specificity first, quality only as a tie-break.
Accept header built
Entries are emitted with q values only where they differ from 1.
q=0 is an explicit refusal rather than a low preference, and a more specific range beats a less specific one whatever the q values say.
Accept: application/json
A q of exactly 1 is the default and is left out, which is what every real client does. Writing it changes nothing and makes the header longer.
Accept Header Builder runs entirely on your device — nothing is uploaded.
You’re on the Free plan. Compare plans
Accept headers behave unexpectedly because of one rule: specificity beats quality. A server picking a representation sorts candidates by how specific the range is first — `text/html` beats `text/*`, which beats `*/*` — and uses the q value only to break ties within one level.
So `Accept: */*;q=1.0, application/json;q=0.5` does not mean "anything, but JSON is acceptable". The JSON range is more specific and wins outright, despite the lower q. That single misunderstanding accounts for most content-negotiation surprises.
A q value is a weight rather than a percentage, and q=0 is not low priority — it is an explicit refusal. `Accept: */*, image/gif;q=0` means anything except GIF, which is a useful and rarely-used construction.
The parse view sorts the ranges the way a server would and says why each one sits where it does, which is the quickest way to see whether the header you are sending means what you think.
A q of exactly 1 is the default and is omitted from generated headers, because writing it changes nothing and makes the header longer. That is what every real client does.
No. Specificity is compared first. `application/json;q=0.5` beats `*/*;q=1.0`, because a fully specific range outranks a catch-all whatever the q values say. q breaks ties within one level of specificity.
An explicit refusal, not a low preference. `Accept: */*, image/gif;q=0` says anything except GIF. A server that honours it will return 406 rather than the refused type.
Three decimal places, and it must be between 0 and 1. A value outside that range is invalid rather than clamped, and some servers reject the whole header rather than the one range.
No. It is the default, so writing it changes nothing and lengthens the header. Generated output here omits it, matching what real clients send.
The server should return 406 Not Acceptable. In practice many return their default representation anyway, which is why a strict Accept header is less of a guarantee than it looks.