Hmmm, Interesting proposition... I know how to do it externally, but not internally to the Apache engine...
CGI --> /www/tmp/343893.shtml (write random file)
___|--> redirect -> /www/tmp/343893.shtml --|
_________________________client browser <--|
This is what I used on the Apache 1.2.x series of servers...
I see 3 options internally
1) internal mod_rewrite with it's output piped and restacked for the SSI handling module
2) internal CGI --> SSI handler (somehow connect/bridge the 2 together)
3) mod_perl should allow me to hook the CGI API and SSI handlers forming a pipelined bridge... (variation of #2)
CGI --> mod_perl API hooks --> SSI (with traps to stop looping)
These are all speculative, and would take me some time to figure out the correct 'voodoo' necessary to do such a thing...
Del, the 'content-type' *may* also work as well, if they have changed the dynamic handling (1.2.x --> 1.3.x)... It just seems *too* easy... :p Haven't had time to test it though -- got my hands full with the new server...
(In other words: I need to research this...)
[This message has been edited by ccTech (edited 11-25-98).]