#15 CGI status reporting

For log accuracy, it would be nice to record in the log the status returned by the CGI (for now, the best this can be is PRIV, ERR! or OK), instead of the status the server wishes to assume. For example:
- a CGI handling errors may return a non-404 code, such as 200 (directory listing), 301 (redirect), etc.
- the action-handler system assumes OK for all requests without performing a file check, so asking for "/nosuch.asp" will pass that request to MacASP and record an OK despite there being so such file.

While it would be possible to permit CGIs to return a reply integer with the status code in, it would be far more backwards compatible to merely read in the first line of the CGI's reply HTTP and use that for recording the CGI's status.