[stephenr]

> when in practice do you want to do that?

Well as you're quite interested in APIs: the accept header is a fantastic way to version a REST API, and even has a built in way to handle clients that can talk to multiple versions of the same API.

Your app could request just 'application/vnd.foo.v1+json' from an API and if it's a centralised service that may be fine.

If the API your app talks to is something that's deployed to customers, or rolls out to regions incrementally or whatever, and thus can be at different versions, you need a way to handle that: the Accept header has you covered.

[Gigachad]

Everyone does this by putting /v1/ in the api url. It's massively more visible, gets logged properly, and isn't annoying to request from tools like curl.

The Accept header does nothing that URLs can not.

[naasking]

> Everyone does this by putting /v1/ in the api url

URLs are opaque identifiers that only have meaning to the server that generated them. This makes any meaning implicit, where the accept header is an explicit and documented part of the interface. Maybe not much difference in practice for code you've interacted with, but that doesn't mean no difference at all.

If curl has trouble setting headers, that's a curl problem.

[stephenr]

You saying "no one needs that" doesn't mean it doesn't do more than some arbitrary url parameter or path segment. It means you're choosing not to use it.

[Gigachad]

If you can choose to not use it, then you don't need it. It doesn't enable any new capabilities.