On Thursday, Jun 5, 2003, at 11:25 US/Pacific, Edson Manners wrote: [..]
[..]Is there anyway I can send the cgi output to a .shtml file before handing it to the browser, or handing this output to the webserver so that it can parse the SSI before giving it to the client browser?
I think that is the basic problem that you are dealing with. You have a 'design pattern' that says
something else will parse my output
for special information, and do stuff with itso You might want to think in terms of say:
#
# we would use an ssi virtual= here were we a
# static html file
# open(VIRTUAL, "fsunetwork_header.html");
print STDOUT $_ while(<VIRTUAL>);
close(VIRTUALsince if the file is going to just be included, then it will 'just be there'....
cf: http://www.webmasterworld.com/forum13/633.htm
what most folks forget about the basic idea of SSI was that it would allow something else to do the actual lifting of including stuff 'on the fly' - whereas coming to the CGI process IS about making it up 'on the fly'.
HTH.
ciao drieux
---
-- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
