The Ethernet cable scissor test success made me laugh :D. We agree on the general weak suitability of http codes to convey application layer status, but I kind

The Ethernet cable scissor test success made me laugh :D. We agree on the general weak suitability of http codes to convey application layer status, but I kind of disagree on the 503 because it implies an overload and an internal error, which is not the case. Also I really believe the resource not a available is as accurate as it gets. In the end I agree with you we may be splitting hairs with a very unsuitable status report and should just send 200 with the error. I have done this before actually, but it tickles my neck a lot to see an OK, then error.