silverwizard
Ok - I've been told that HTTP 418 belongs in the 400 block because it's the same as requesting a non-existent file. This argument claims that 418 is the same as 404.
I tend to think of 418 as being more analogous to 501. You cannot put coffee in a teapot, which is a statement about the teapot.
⛅ w chance of bears
You can put coffee in a teapot, though. The rejection is administrative.
silverwizard
hypolite
⛅ w chance of bears
@silverwizard It's like rejecting form data that's of the right type based on validation against the field's semantics. Which would be 400 series.
silverwizard
⛅ w chance of bears
@silverwizard A teapot is mechanically a vessel that implements a catch-all "add liquid" or "pour liquid" more-or-less transparently to the actual identity of the liquid (barring extreme properties). When trying to put coffee in a teapot the method is implemented and the data would be valid, except that the teapot czar intervenes with an externally imposed rule which adjudicates that the data is actually invalid because reasons. 403 Forbidden.
silverwizard
⛅ w chance of bears
@silverwizard I'm looking at this as a web application returning a response code. HTTP is a protocol; some of the participants of that protocol will be extremely content aware, others less so. The very notion that holding coffee violates a teapot's nature is a philosophical conceit that would be odd for a low awareness system to express in the first place.
On the other hand, I suppose that attempting to french press in a teapot would be my idea of a 500-series teapot error.
silverwizard
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.