418 I’m a teapot
developer.mozilla.org
418 I’m a teapot
1–10 of 146 posts
Re: 418 I’m a teapot
#2Discussions in:
2020 (153 points, 118 comments) https://news.ycombinator.com/item?id=24206899
2021 (193 points, 108 comments) https://news.ycombinator.com/item?id=28541327
2023 (206 points, 189 comments) https://news.ycombinator.com/item?id=36090344
Re: 418 I’m a teapot
#3Re: 418 I’m a teapot
#4Here I was, foolishly thinking it was code for operator panic: https://www.youtube.com/watch?v=kLQStcdhAGA
Re: 418 I’m a teapot
#5you are not a tea pot.
Re: 418 I’m a teapot
#6Please, never ever again add such features to standards as a joke. Some backend folks have started to return it as an indetermiante error code, which in turn means that all client-side libraries will have to handle it at some level.
Re: 418 I’m a teapot
#7Please, never ever again add such features to standards as a joke. Some backend folks have started to return it as an indetermiante error code, which in turn means that all client-side libraries will have to handle it at some level.
* get to handle it.
Re: 418 I’m a teapot
#8Please, never ever again add such features to standards as a joke. Some backend folks have started to return it as an indetermiante error code, which in turn means that all client-side libraries will have to handle it at some level.
Why is this a problem for libraries? Not that most libraries handle anything about HTTP correctly out of the box anyway.
Re: 418 I’m a teapot
#9Please, never ever again add such features to standards as a joke. Some backend folks have started to return it as an indetermiante error code, which in turn means that all client-side libraries will have to handle it at some level.
Well, I recently used it in a small PostgREST-subset query builder I wrote in case the query builder received an input more complicated that what it could handle. I found 418 a natural response in this case. In retrospect a 5xx (edit: or better 422) error is more appropriate, however.
Re: 418 I’m a teapot
#10Please, never ever again add such features to standards as a joke. Some backend folks have started to return it as an indetermiante error code, which in turn means that all client-side libraries will have to handle it at some level.
Thankfully, error codes such as this are structured so that the initial "4" digit is the only one that really matters. Just treat it as a client error and you can't go wrong.