From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: From: Charles Forsyth To: 9fans@cse.psu.edu Subject: Re: [9fans] httpd scripting In-Reply-To: <3EDB4C63.5080902@proweb.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Date: Mon, 2 Jun 2003 14:51:18 +0100 Topicbox-Message-UUID: c2802d20-eacb-11e9-9e20-41e7f4b1d025 i looked at the code, and the rule i used was simply that if the url for GET and POST corresponded to an executable file-- as gdb suggested not just an rc file, though i did use rc for many examples-- httpd forked the name space (having originally secured it) and environment, put some of the parsed data in the environment (could have served it up in files), optionally sent an HTTP reply header, and ran the program. if the executable file's suffix was .http, it was assumed to generate its own HTTP headers, otherwise httpd provided whatever was appropriate to the file's suffix.