Re: advice on httpd sought (Rob McCool)
X-Delivered: at request of secret on
Message-id: <>
From: (Rob McCool)
Date: Wed, 6 Oct 1993 22:11:39 -0500
In-Reply-To: Lou Burnard <>
       "advice on httpd sought" (Oct  6,  6:19pm)
X-Mailer: Mail User's Shell (7.2.5 10/14/92)
To: Lou Burnard <>,
Subject: Re: advice on httpd sought
 * advice on httpd sought  by Lou Burnard (
 *    written on Oct  6,  6:19pm.
 * I can't believe I'm alone in wanting to do this. Nor that no-one has
 * thought of this way of doing it. Would someone therefore please very
 * kindly tell me (and preferably offline if I am asking a really dim
 * question)  how to tell my httpd server that when it gets a request for a
 * document with extension .blort it should pass said document through a
 * filter FOO before serving it forth? I glanced through the httpd v 0.4
 * from ncsa, but couldn't see any obvious place to do it. Before I roll up
 * my shirtsleeves and get hacking, I'd just like to find out if someone's
 * passed this way before... 

In NCSA httpd 1.0a2, you could do this, although not quite as you are
asking. What you would probably do is have a script (which is your filter)
in /htbin, let's call it foo. HREF's to the TEI documents could then be
something like /htbin/foo?/the/document/name.blort.

In later releases, we're going to change the script interface such that when
looking in the scripts directory, if it finds an executable early, it will
send the rest of the path as an argument to the script. In this
architecture, your documents would be referenced by something like:


And the script execution would be transparent.

 * Why do I want to do this? because I expect to have several zigaflops of
 * TEI-conformant sgml text here is why, and I really don't want to have
 * to keep copies of them all online in html as well. Writing a filter
 * to translate TEI markup into html is well within the bounds of even
 * my C-competence.
 * thank you
 * Euro-Lou

Hope this helps