I replied to the following: ↷

Simon Willison (@simon@simonwillison.net)

Unpopular opinion time: I don't like the #HTTP Accept headerAny time I encounter it I find it surprising, and it inevitably makes web APIs both harder to work with and harder to understandPlus it can break things in very subtle and surprising waysDid you know Cloudflare used to ignore "Vary: accept" entirely? And today only respects it for image formats?Which presumably means you can't put a Mastodon instance behind Cloudflare because some Mastodon APIs need "Accept: application/json"
byMastodon archived copycurrent

Could one say that it's Cloudflare not conforming to specs w.r.t HTTP? Obviously, there's smarter people there than me (but I also don't touch their services anymore for ethical reasons) but I could imagine there's some sort of document that they have explaining this.

That said, what would you do in place of the header? Adjusting the URL?

Engagement is powered by Webmentions — a premier standard of the Web to let other sites know you've mentioned them. Learn how to reply from your own site. or from a supported silo Aaron has an interactive post about this. If you've mentioned this URL via another one, use the form below to submit it.

If you don't currently own your replies, then you can click below to do so.

I currently aim to own my comments and plan to eventually show those I've received once I finish Lighthouse.