[Ur] CGI executables and parsed header format

[Adam Chlipala]

Changing the CGI backend to use parsed headers everywhere sounds fine to 
me.  Such an approach wouldn't work for other backends, like direct 
HTTP, right?  There it is necessary to include the status code in the 
first line of the server's response.

On 02/23/2013 01:00 PM, Benjamin Barenblat wrote:
> I noticed today that CGI Ur/Web executables use the parsed header output
> format [1]...except on error (304 or 404), in which case they use the
> non-parsed header format [2].  Having this split behavior, while
> technically within standard, seems silly; can I [submit a patch to the
> compiler to] switch executables to parsed headers everywhere?
>
> Benjamin
>
>
> [1] https://tools.ietf.org/html/draft-robinson-www-interface-00, §9.2
> [2] ibid., §9.1
>