Re: OLD CGI CALLS

Adam R. B. Jack writes:
 > On Sun, 23 Jun 1996, Anselm Baird-Smith wrote:
 > The following five lines constituts the diff output for this change.
 > 228c228
 > < 	addEnv ("SERVER_NAME", server.getHost(), env) ;
 > ---
 > > 	addEnv ("SERVER_NAME", "jigsaw", env) ;

Yep, BTW the server name will end up being a property, so that people
using Jigsaw for to build their 'own' server can have their own
nbame...

 > If I run accross any more I will email them.

Thanks,

 > The CGI software I am using is an HTML preprocessor for file with a certain 
 > extn. It parses the HTML for special 'extension' tags and replaces them with 
 > dynamically generated HTML output as appropriate. Sometimes it find no tags 
 > to replace and returns a local redirect to the file. (Note: Then why have
 > this extension on the file? Dont ask me! Lame I know -- hence the low
 > priority.) Anyway, such redirects would, on a normal server, be:
 > 
 > 	..../cgi-bin/BLAH?/blah_dir/blah.XXX redirected to
 > 	..../blah_dir/blah.XXX
 > 
 > Obviously -- I find that I can no longer depend upon extension XXX to determine
 > if a resource should be a CgiResource. (It forces the browser into a potentially
 > infinite redirect loop, which Lynx, and I assume the HTTP protocol, is too 
 > smart for.)

I am missing something here ? Isn't the name of your script
/cgi-bin/BLAH, and its query string /blah_dir/blah.XXX ? In such case,
why not simply register the BLAH script as a CgiResource (m,anually),
and keep the XXX extension for your server side include machanism (I
realize that I am defintely missing something).

Could you provide more infos on your stuff ? What I understand is the
following: you have a script BLAH that given (as a request string) the
URL of some other resource, will expand some of the tags in it. If
this is correct, then there ought to be a way to do so with Jigsaw...

Anselm.

Received on Sunday, 23 June 1996 16:59:23 UTC