Thank you Masakazu. That's good feedback. I didn't think of how the empty
reason phrase is a strong hint of what is going on in the backend.
As I investigated things further, it turns out we already have an
implementation of a default reason phrase. I'm working on applying the use
of it to this si
Let's refer to the latest specs.
https://www.rfc-editor.org/rfc/rfc9112.html#name-status-line
The reason-phrase is optional, but the SP between status-code and
reason-phrase is not. The spec clearly states it.
status-line = HTTP-version SP status-code SP [ reason-phrase ]
> A server MUST send th
dev@trafficserver.apache.org:
The current master (10.x) branch has HTTP/2 to origin support. The HTTP/2
protocol has officially removed reason phrases from the RFC:
https://www.rfc-editor.org/rfc/rfc7540.html#section-8.1.2
HTTP/2 does not define a way to carry the version or reason phrase that is
