2 ms·
> One reason why it's bad is because it violates RFC 2616 RFC 2616 is obsolete, as are the RFCs which obsoleted it; the reference here should be to §15 of RFC
by dragonwriter 3y ago
> One reason why it's bad is because it violates RFC 2616
RFC 2616 is obsolete, as are the RFCs which obsoleted it; the reference here should be to §15 of RFC 9110.
- jmholla 3y agoIt should be noted that nearly the same verbiage presented by the GP is used in RFC 9110. RFC 9110 also goes further to explicitly say that 999 is an invalid error code, but does indicate they should be treated as a 5xx. > Values outside the range 100..599 are invalid. Implementations often use three-digit integer values outside of that range (i.e., 600..999) for internal communication of non-HTTP status (e.g., library errors). A client that receives a response with an invalid status code SHOULD process the response as if it had a 5xx (Server Error) status code.
- dragonwriter 3y ago> It should be noted that nearly the same verbiage presented by the GP is used in RFC 9110. Yes, in case it wasn't clear, my intent was to correct the reference only, not the substance communicated by the reference.