One of the most irritating bugs in client libraries is if they hard-code 1xx behavior to particular numbers, rather than treating the entire range uniformly.

This makes it easy to desync, though since it's not the server end it's rarely as catastrophic.

To fix this, servers need to start returning bogus 199 Fix Your Client headers before a random fraction of all real responses.

I read the url as: ever t-pot, as a reference to 418. Turns out it's the author's actual name.

Title should probably be updated to include the fact that this is from 2018 (relevant as this series has been completed as opposed to having just been started)

Dang these are much more useful than my first port of call for looking up http codes... which is http.cat/<code>. It's a shame you have to know what a code is to get to it... e.g. /404-not-found works instead of /404

I thought I was conversant in HTTP status codes, even the WebDAV ones, but "226 IM Used" was a new one for me. I wonder why content negotiation wasn't sufficient for this?

It's a great idea to blog through a "mundane" thing like this. You learn alot and have an impetus and won't run out of ideas to blog. There is always another status code! You could do the same with other things. E.g. programming languages or whatever.