If you make up HTTP error codes #cloudflare please add a text reason

HTTP/2 522

gets translated by Firefox to

Error code: 522 No Reason Phrase

Needing a google search to find out that this is a cloudflare-specific code that looks an awful lot like a duplication of HTTP error status 504 Gateway Timeout is not very helpful

@KHoos I shared this with folks internally (at Cloudflare).

Learned that https://cloudflare.com/cdn-cgi/error/{error code} provides additional information on error codes. Sharing as an FYI.

@dbelson indeed https://cloudflare.com/cdn-cgi/error/522 gives a usable explanation.
The missing 'reason phrase' in protocol is still an omission in my opinion.
I appreciate you looking at this and sharing it!

@KHoos @dbelson FWIW neither HTTP/2 or HTTP/3 define any means to emit a reason phrase. See e.g. https://datatracker.ietf.org/doc/html/rfc9114#section-4.3.2

The screenshot demonstrates the user-agent attempting to be helpful by mapping well known codes back to human-readable reason phrases. Any code they don't support, even standardized ones yet implemented, could not be mapped

RFC 9114: HTTP/3

The QUIC transport protocol has several features that are desirable in a transport for HTTP, such as stream multiplexing, per-stream flow control, and low-latency connection establishment. This document describes a mapping of HTTP semantics over QUIC. This document also identifies HTTP/2 features that are subsumed by QUIC and describes how HTTP/2 extensions can be ported to HTTP/3.

IETF Datatracker