httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Luc I. Suryo" <>
Subject Re: [users@httpd] Trying to get SSI directives processed after request has been processed by Tomcat app server.
Date Wed, 26 Apr 2006 17:31:05 GMT

hope this could help other

Apache 2.0.54 (Unix / Solaris)
tomcat 5.0.28 (Unix / Solaris)

module installed: mod_jk2, allowing us to pass certain directories that
are j2eee/java program back to Tomcat..(tomcat is on the back-end in a
dmz). So traffice for is then handled
by Tomcat on port 8231, works well.

Our looks like this:

#----- start -----
info=Ajp13 forwarding over socket

info=Map the whole webapp for data_scores
#----- end -----

as you can see pretty easy, 

check :


> Seems you've gotten two different responses to this John.  This is 
> something that I just may be wondering
> about in the future myself, so if you can post back to the list whether you 
> were successful or not that wuold
> be appreciated!
> -Dave
> ----- Original Message ----- 
> From: "Pyeatt, John" <>
> To: <>
> Sent: Tuesday, April 25, 2006 4:35 PM
> Subject: [users@httpd] Trying to get SSI directives processed after request 
> has been processed by Tomcat app server.
> I am working with a customer with the following basic configuration. They 
> are running Apache 1.3.33 and make heavy used of mod_include.
> A new project has come up that uses J2EE web applications. Our intent was 
> to have Apache forward requests for .jsp to Tomcat 5 (running on a separate 
> server) via mod_jk.The JSP-generated response would include SSI directives 
> which would subsequently be processed by mod_include on httpd just prior to 
> heading out the wire back to the browser.
> I suspect the short answer is "you can't do that". If it can be done I 
> would appreciate any guidance with httpd.conf configuration that would work.
> If the answer is "you can't do that in Apache 1.3.*, but you can in Apache 
> 2.*" then I can investigate that option.
> I understand the configuration I am talking about is very goofy. The reason 
> for goofiness would take pages to explain and besides, if everything were 
> simple, we'd all be out of work.

The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:> for more info.
To unsubscribe, e-mail:
   "   from the digest:
For additional commands, e-mail:

View raw message