sanitation@lemmy.today to Programming@programming.dev · 27 days agoRFC 10008: The HTTP QUERY Methodwww.rfc-editor.orgexternal-linkmessage-square7fedilinkarrow-up148arrow-down11
arrow-up147arrow-down1external-linkRFC 10008: The HTTP QUERY Methodwww.rfc-editor.orgsanitation@lemmy.today to Programming@programming.dev · 27 days agomessage-square7fedilink
minus-square9point6@lemmy.worldlinkfedilinkarrow-up7·edit-227 days agoThis is pretty good, though I expect even if it’s accepted it’s going to be a long journey before you can reliably use it If we’re adding stuff to http, it would be nice for some additional status codes, things have moved on a bit since the early days
minus-square[object Object]@lemmy.calinkfedilinkarrow-up15·27 days agoThere should be a 400 that just says “fuck you and your AI”
minus-squarecalliope@retrolemmy.comlinkfedilinkarrow-up11·27 days agoI believe you can use 422: Unprocessable Content for this. The request was well-formed (i.e., syntactically correct) but could not be processed. “I know what you said, but I’m not answering you.”
This is pretty good, though I expect even if it’s accepted it’s going to be a long journey before you can reliably use it
If we’re adding stuff to http, it would be nice for some additional status codes, things have moved on a bit since the early days
There should be a 400 that just says “fuck you and your AI”
I believe you can use 422: Unprocessable Content for this.
“I know what you said, but I’m not answering you.”
That’s what 418 is for imo