what the FUCK is this guys problem?? https://github.com/gol

A HTCPCP/1.0 return code was implemented as HTTP/1.0 return code. That is a HTTP protocol violation.
The ticket is valid. What is *your* problem with the it?

not OP, but problem might be that it's there in the first place

The issue reporter is one of the few rational people in that thread. 418 isn't real, and the authors of the RFC were careful to make sure they were talking about HTCPCP instead of HTTP for exactly this reason.

>>61852768
t. Mark

ITT: boring ppl who hate fun

here's a fun fact, you can send any three-digit status code with any ascii status message and additionally use any verb and any headers and it all JUST WORKS™

HTTP/1.1 FUCK /my/ass
Using-Lube: "no"

HTTP/1.1 888 Seig Heil

rigorously enforcing loosely defined things like http status codes has to be the most blatantly pedantic bureaucratic WASTE OF TIME I've ever encountered

all things considered, it's exactly like enforcing codes of conduct and word choices like master/slave which you people normally get all up in arms about you fucking HYPOCRITES dont' ttalk to me or my eggplant ever again

>>61849883
>was it autism?
nope, oughtism - it ought not be included in any implementation.