3 ms·
At the point in the distant future where you are worried about needing more HTTP error codes and considering reusing 418 it may just be easier to just add more
by WorldMaker 9y ago
At the point in the distant future where you are worried about needing more HTTP error codes and considering reusing 418 it may just be easier to just add more digits to the protocol. In HTTP/1.x the status codes are plaintext and it's not like it would be that much of a change to most HTTP parsers. There's not really even a strong technical reason why they are three digit codes to begin with in plaintext HTTP, it's just an arbitrary choice.
The HTCPCP argument isn't all that valid as there are several recognized (IANA) HTTP codes [1] from HTTP extensions like HTCPCP. Note for instance all the ones from rfc4918 which is the WebDAV extension to HTTP, such as 424 and 507. Not all codes are from HTTP RFCs and I also think the "bug" here is that IANA has ignored rfc2324 for too long and should recognize the RFC as a valid HTTP extension with useful [2] HTTP status codes.
[1] https://www.iana.org/assignments/http-status-codes/http-status-codes.xhtml https://www.iana.org/assignments/http-status-codes/http-stat...
[2] Usefulness is a subjective measure, of course, but usefulness in jokes/play is still usefulness.