Httpd tests

• Access restriction by IP-address. (I test with modified config files on a non-standard port; these restrict access from outside the AI lab, for obvious reasons. If that restriction is not in effect --- which is easy enough to test --- the thing gets instantly flushed).
• CGI script through standard interface. Retrieving this page tests GET; the embedded form tests POST. This shows you the CGI vars --- PATH_INFO should be /path/info. It also adds a few MIME headers to the output --- telnet to the server to see them.
• CGI script through ScriptAlias. Same thing as above, different route.
• CGI script through locally modified interface.
• Server-side includes test page. Note that the embedded CGI script should have the QUERY_STRING var set to "query string" --- this is from the URL in this document, not from the <!-- exec ... --> directive.
• Stalemate Project publications office. A set of CGI-scripts which checks authentication, and the interaction between authentication and scripts. (Some of the scripts read the authentication info, and present different output to different authorized users).
• A simple NPH- script
• The lab home page
• An image mapping experiment. Click on parts of the locomotive to find their names --- in the names of the files in the 'Not Found' error messages. It's enough to verify that the mapping machinery is working, at any rate.
• Testing under load --- at least five minutes of logfile replay at five transactions/second.