nafyi.

A TOPIC, IN CONTEXT

API design preference

Judgments in this source concerning API design preference. Explore 1 viewpoint with evidence from 1 source.

1 people · 1 sources · 1 viewpoints

Content updated:

Explore connections ↗

Viewpoint map

Explore by person. Select two or three to compare.

1 people · 1 sources · 1 viewpoints

Simon Willison

Preference for URL-based content negotiation over Accept headers

Simon Willison independently chose not to use Accept-header–based content negotiation, preferring predictable URLs—for example, using a '.json' suffix to serve JSON.

Comment: We just shipped support for the ugliest part of HTTP: Vary

Supporting evidence

Simon Willison·

Comment: We just shipped support for the ugliest part of HTTP: Vary

Original excerpt

(Independent of the Cloudflare feature I ended up deciding never to use that pattern, because I prefer having URL that predictably returns HTML or JSON - I add a .json suffix to my apps to serve JSON instead.)
Open original · Paragraph 5 (opens in a new tab)Original text source (opens in a new tab)
Share insightCheck this claim

These are individual perspectives, not a measure of consensus. Source material stays in its original language.

Original conversations1

ARTICLE

Comment: We just shipped support for the ugliest part of HTTP: Vary

Simon Willison's Weblog