Http needs a status code for grudging acceptance.
-
Http needs a status code for grudging acceptance. We have 202 Accepted. We need 222 Tolerated.
For when the client is doing it wrong, but you've decided to be the bigger person and deal with it anyway.
-
Scott Gallowayreplied to Jenniferplusplus on last edited by
@jenniferplusplus Isn't 222 already used for Auth succeeded? 218 is 'this is fine' which seems sufficiently passive agressive
-
Jenniferplusplusreplied to Scott Galloway on last edited by
@scottgal 218 was made up by apache. I found no reference to an existing 222 code
-
Kevin Granadereplied to Jenniferplusplus on last edited by
@jenniferplusplus 242 Watch It Buster
-
Scott Gallowayreplied to Jenniferplusplus on last edited by
@jenniferplusplus Non standard but mentioned here. https://www.kinexmedia.com/blog/http-status-codes/ few mentions though so suspect it's just one or two servers which pass it.
-
Scott Gallowayreplied to Scott Galloway on last edited by
@jenniferplusplus I used to work for a company where they'd 'entertainingly' used 418 for every error response.
-
Jenniferplusplusreplied to Jenniferplusplus on last edited by
Actually, what I *really* want is a 3xx with a body.
322 Translated
Here's how you should have written that request, now go back to your seat and do it over -
Jenniferplusplusreplied to Scott Galloway on last edited by
@scottgal that would be unhelpful
-
Jenniferplusplusreplied to Jenniferplusplus on last edited by
I'm doing activitypub things, and contemplating such quirks as the fact that there is no limit to the kind or depth of activities that can be the object of an undo activity.
In case you're wondering what prompted this.
-
@jenniferplusplus "your request is such a mess I can't even tell specifically what's wrong with it, please go away" but I guess that's already 400
-
Malcolm Herbertreplied to Jenniferplusplus on last edited by
@jenniferplusplus I feel the browser needs a voice at some point in this also - I asked for a plain page and you gave me this unparseable dreck?
-
@jenniferplusplus In that case we also need the opposite, HTTP 444 Technically Correct But Still No.
-
Greg Kempreplied to Jenniferplusplus on last edited by
@jenniferplusplus I don’t know why but this whole thread made me laugh maniacally this morning. Thanks for that.
-
0xC0DEC0DE07E8replied to Jenniferplusplus on last edited by
@jenniferplusplus (There needs to be an error code that means “I received your request but decided to ignore you.”)
- Rogue Protocol: The Murderbot Diaries -
CM Harringtonreplied to Malcolm Herbert on last edited by
@mherbert @jenniferplusplus ‘I parse HTML, why the fuck are you sending me JSON?!?’
-
Jenniferplusplusreplied to Jenniferplusplus on last edited by
Kind of ridiculous that this is now one of my top ten fedi posts, by the numbers
-
Jenniferplusplusreplied to Jenniferplusplus on last edited by
oh, a couple of points:
1. 429 is the status code that means things like "I'm ignoring you" or "stop doing that"
A "tolerated" response code could feed into a fail2ban-like system that escalates to 429s.
2. I don't know why so many people think this is a joke?. It's barely even shitposty. And it's a real desire. I do genuinely want these things.
-
@[email protected] @[email protected] That's what
406 Not Acceptableis for, heh. -
Rafael Ribeiroreplied to Jenniferplusplus on last edited by
@jenniferplusplus that's facts.
-
eepy catreplied to Jenniferplusplus on last edited by
@[email protected] for real. I would use the heck out of that for deprecated/undocumented requests. Especially if clients knew to log it as like "this works...for now..." so it's on them if they don't fix it before we break it.
