Post

Oh. After many long years... HTTP now officially has a standard QUERY method. Think: cacheable, idempotent GET that can carry a meaningful payload. We can now all stop bastardizing POST. auth48-transition.rfc-editor.org/authors/rfc1...

auth48-transition.rfc-editor.orgauth48-transition.rfc-editor.org

14/6/26, 12:40 pm14 reposts71 likes

yak

@yakmol.bsky.social

15 June

@snell.zone you may be interested in this as the original poster’s name is similar to yours

Peter Mbanugo

@pmbanugo.me

14 June

The link to the RFC editor in the PDF is broken. This takes me to a 404 www.rfc-editor.org/info/rfc10008 I wanted to check if it’s already approved.

rfc-editor.orgrfc-editor.org

Apiark

@apiark.bsky.social

21 July

Long overdue. The part I'm curious about is intermediaries: a proxy or gateway that's never heard of QUERY has to decide whether to forward it as-is or fall back to treating it as unsafe. Any sense of how CDNs and API gateways are lining up to support it, or is this a wait a year and see situation?