> On Mar 17, 2026, at 3:50 PM, [email protected] wrote: > > +<p>Note: httpd only supports status codes that are included in the HTTP > +spec. Using an unrecognized status code will result in a 500 error and > +error log message.</p>
Yep, though "fixing" this could be a good short project. Basically, we assume that the canonical list of status codes can be defined at compile time, which is only needed for matching codes to reason phrases. We still want to keep that for backwards compatibility, but our own parser/output could be a lot more flexible. IOW, validate the code and if it isn't in the defined set then allow it to be treated as the x00 code (i.e., 100, 200, 300, 400, 500) and use "undefined" as the reason phrase. We should only generate our own 500 error if the present status isn't valid syntax. Note that the easy part is fixing the error case. The hard part is finding all of the code that currently assumes we are going to error on undefined codes. ....Roy
