[Ur] CGI executables and parsed header format

[Benjamin Barenblat]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Howdy all,

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
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iQEcBAEBCgAGBQJRKQOqAAoJEJ5zAUnrkcU7teAH/RQASxjkrqEFZxnAhoARs0Cr
anU9RI20L9Nd9Ud42y0w0hj2Xr2DH1CA8okys5UwJl34Z4Rpc5fATeELB/OSaSyg
H2xek3QMEHbeJh/pz3xThJQScaFZO3m/KDBdVMKlrr0i3Z9K6qc/6ToIqrYMMnwu
8FjurhqeGbOrjEVBTkXaqxI2fmh02m0HXIRCXXvqjtzI2rSilOrccs9V/bXcUe2k
dH+rts+khxLAagDS85OB6kl8ey21JCwy1rT8r3UkZihs3zJpzpNBQHVZizIGh3/o
kVwd2Mp/OBBsNVdE9jJgDLYaGeKJhbythMVVoqJ8LP7JaaAq+t/WaVJnG2idVDM=
=wGpq
-----END PGP SIGNATURE-----