Rusty, From what I have read, you get better performance if you let tomcat serve the static stuff as well as the jsps. Check the tomcat docs for a discussion of this topic.
However, if you still want to put tomcat behind apache, take a look at this article - tomcat.apache.org/tomcat-4.1-doc/ssi-howto.html (the link is down now - try it in a while) or google "tomcat ssi". The gist of the article is that you need to download a jar file, add it to your classpath, and then tomcat will serve ssi directives correctly. Mark On Monday 12 December 2005 11:26 pm, [EMAIL PROTECTED] wrote: > I'm talking about having tomcat behind apache, with apache serving > static content and tomcat serving generated html (or whatever) > content. Your jsp include suggestion would only work for static > content in the tomcat dir. > > See below after your included message my response to Martin, which may > help explain what I'm talking about. > > From: Mark Phillips <[EMAIL PROTECTED]> > Organization: Phillips Marketing, Inc. > To: users@tomcat.apache.org > Subject: Re: setup for web designers? > Date: Mon, 12 Dec 2005 21:20:44 -0700 > Cc: [EMAIL PROTECTED], > "[EMAIL PROTECTED]" <users@tomcat.apache.org> > > Try using <%@ include file="header.html" %> instead. > > Mark > > On Monday 12 December 2005 06:29 pm, [EMAIL PROTECTED] wrote: > > How do people set up their tomcat so that the web designers can work > > on the static content and the programmers can work on the jsp stuff > > without stepping on each other's toes? > > > > In my case the web designers have already been working with apache > > with their files in /usr/local/apache/htdocs. > > > > My first thought is to put tomcat behind apache with mod_jk but after > > some minimal testing I discovered that apache server side includes > > don't work; for example, if the html from my jsp has <!--#include > > virtual="/header.html"--> that line isn't replaced and is sent to the > > browser. > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > -- > Mark Phillips > Phillips Marketing, Inc > [EMAIL PROTECTED] > 602 524-0376 > 480 945-9197 fax > > > Date: 12 Dec 2005 22:17:29 -0800 > From: <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: Re: setup for web designers? > > I did look at that but that's just for apache. If you think about it, > the two directives > > AddType text/html .shtml > AddHandler server-parsed .shtml > > tell apache to look at the extensions of the files, on disk. What I'm > talking about is html data that's coming to apache directly over the > ajp13 socket, from tomcat, in which case there's no file extension. > When you run tomcat connected to apache with mod_jk you're running > tomcat behind apache. The output from tomcat is piped through apache > and then sent to the browser. Going the other way, the requests from > the browser go through apache and are sent to tomcat. > > I need some way to turn on the "AddHandler server-parsed" for > everything coming in to apache from tomcat over the ajp13 mod_jk > socket. Or some way to make it think that everything coming from > tomcat is an .shtml file. > > From: "Martin Gainty" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Subject: Re: setup for web designers? > Date: Mon, 12 Dec 2005 21:47:18 -0500 > > This is a multi-part message in MIME format. > > ------=_NextPart_000_0061_01C5FF65.9FD7D8B0 > Content-Type: text/plain; > charset="iso-8859-1" > Content-Transfer-Encoding: quoted-printable > > Rusty > Take a look at = > > http://httpd.apache.org/docs/1.3/howto/ssi.html#configuringyourservertope= > rmitssi > > > Configuring your server to permit SSI > To permit SSI on your server, you must have mod_include installed and = > enabled. Additionally, you must have the following directive either in > = your httpd.conf file, or in a .htaccess file: > > Options +Includes > This tells Apache that you want to permit files to be parsed for SSI = > directives. Note that most configurations contain multiple Options = > directives that can override each other. You will probably need to > apply = the Options to the specific directory where you want SSI enabled in > = order to assure that it gets evaluated last. > > Not just any file is parsed for SSI directives. You have to tell Apache > = which files should be parsed. There are two ways to do this. You can = > tell Apache to parse any file with a particular file extension, such as = > shtml, with the following directives: > > AddType text/html .shtml > AddHandler server-parsed .shtml > HTH,Martin > > ------ Original Message -----=20 > From: <[EMAIL PROTECTED]> > To: "[EMAIL PROTECTED]" <users@tomcat.apache.org> > Sent: Monday, December 12, 2005 8:29 PM > Subject: setup for web designers? > > > How do people set up their tomcat so that the web designers can work > > = > > on the=20 > > > static content and the programmers can work on the jsp stuff > > without=20 stepping on each other's toes? > >=20 > > In my case the web designers have already been working with apache = > > with=20 > > > their files in /usr/local/apache/htdocs. > >=20 > > My first thought is to put tomcat behind apache with mod_jk but after > > = > > some=20 > > > minimal testing I discovered that apache server side includes don't = > > work;=20 > > > for example, if the html from my jsp has <!--#include=20 > > virtual=3D"/header.html"--> that line isn't replaced and is sent to = > > the=20 > > > browser.=20 > >=20 > >=20 > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > >=20 > > ------=_NextPart_000_0061_01C5FF65.9FD7D8B0 > Content-Type: text/html; > charset="iso-8859-1" > Content-Transfer-Encoding: quoted-printable > > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> > <HTML><HEAD> > <META http-equiv=3DContent-Type content=3D"text/html; = > charset=3Diso-8859-1"> > <META content=3D"MSHTML 6.00.2900.2769" name=3DGENERATOR> > <STYLE></STYLE> > </HEAD> > <BODY> > <DIV><FONT face=3DArial size=3D2>Rusty<BR>Take a look at </FONT><A=20 > > href=3D"http://httpd.apache.org/docs/1.3/howto/ssi.html#configuringyourse= > rvertopermitssiH"><FONT=20 > face=3DArial=20 > > size=3D2>http://httpd.apache.org/docs/1.3/howto/ssi.html#configuringyours= > ervertopermitssi<BR><BR></FONT></A> > <H2><A id=3Dconfiguringyourservertopermitssi=20 > name=3Dconfiguringyourservertopermitssi><FONT face=3DArial = > size=3D2>Configuring your=20 > server to permit SSI</FONT></A></H2> > <P><FONT face=3DArial size=3D2>To permit SSI on your server, you must = > have </FONT><A=20 > href=3D"http://httpd.apache.org/docs/1.3/mod/mod_include.html";><FONT = > face=3DArial=20 > size=3D2>mod_include</FONT></A><FONT face=3DArial size=3D2> installed = > and enabled.=20 > Additionally, you must have the following directive either in your = > httpd.conf=20 > file, or in a .htaccess file:</FONT></P><PRE><FONT face=3DArial = > size=3D2> Options +Includes > </FONT></PRE> > <P><FONT face=3DArial size=3D2>This tells Apache that you want to > permit = files to be=20 > parsed for SSI directives. Note that most configurations contain = > multiple=20 > </FONT><A = > > href=3D"http://httpd.apache.org/docs/1.3/mod/core.html#options";><FONT=20 > face=3DArial size=3D2>Options</FONT></A><FONT face=3DArial size=3D2> = > directives that can=20 > override each other. You will probably need to apply the Options to the > = specific=20 > directory where you want SSI enabled in order to assure that it gets = > evaluated=20 > last.</FONT></P> > <P><FONT face=3DArial size=3D2>Not just any file is parsed for SSI = > directives. You=20 > have to tell Apache which files should be parsed. There are two ways to > = do this.=20 > You can tell Apache to parse any file with a particular file extension, > = such as=20 > shtml, with the following directives:</FONT></P><PRE><FONT face=3DArial > = size=3D2> AddType text/html .shtml > AddHandler server-parsed .shtml > <BR>HTH,<BR>Martin-</FONT></PRE></DIV> > <DIV><FONT face=3DArial size=3D2>----- Original Message ----- </FONT> > <DIV><FONT face=3DArial size=3D2>From: <</FONT><A=20 > href=3D"mailto:[EMAIL PROTECTED]"><FONT face=3DArial=20 > size=3D2>[EMAIL PROTECTED]</FONT></A><FONT > face=3DArial=20 size=3D2>></FONT></DIV> > <DIV><FONT face=3DArial size=3D2>To: "</FONT><A=20 > href=3D"mailto:[EMAIL PROTECTED]"><FONT face=3DArial=20 > size=3D2>[EMAIL PROTECTED]</FONT></A><FONT face=3DArial size=3D2>" > = <</FONT><A=20 > href=3D"mailto:users@tomcat.apache.org";><FONT face=3DArial=20 > size=3D2>users@tomcat.apache.org</FONT></A><FONT face=3DArial=20 > size=3D2>></FONT></DIV> > <DIV><FONT face=3DArial size=3D2>Sent: Monday, December 12, 2005 > 8:29=20 PM</FONT></DIV> > <DIV><FONT face=3DArial size=3D2>Subject: setup for web=20 > designers?</FONT></DIV></DIV> > <DIV><FONT face=3DArial><BR><FONT size=3D2></FONT></FONT></DIV><FONT = > face=3DArial=20 > size=3D2>> How do people set up their tomcat so that the web = > designers can work=20 > on the <BR>> static content and the programmers can work on the jsp > = stuff=20 > without <BR>> stepping on each other's toes?<BR>> <BR>> In my > = case the=20 > web designers have already been working with apache with <BR>> their > = files in=20 > /usr/local/apache/htdocs.<BR>> <BR>> My first thought is to put = > tomcat=20 > behind apache with mod_jk but after some <BR>> minimal testing I = > discovered=20 > that apache server side includes don't work; <BR>> for example, if = > the html=20 > from my jsp has <!--#include <BR>> virtual=3D"/header.html"--> > = that line=20 > isn't replaced and is sent to the <BR>> browser. <BR>> <BR>> = > <BR>>=20 > > ---------------------------------------------------------------------<BR>= > > To=20 > unsubscribe, e-mail: </FONT><A=20 > href=3D"mailto:[EMAIL PROTECTED]"><FONT > face=3DArial=20 > size=3D2>[EMAIL PROTECTED]</FONT></A><BR><FONT = > face=3DArial=20 > size=3D2>> For additional commands, e-mail: </FONT><A=20 > href=3D"mailto:[EMAIL PROTECTED]"><FONT face=3DArial=20 > size=3D2>[EMAIL PROTECTED]</FONT></A><BR><FONT face=3DArial > = size=3D2>>=20 > <BR>></FONT></BODY></HTML> > > ------=_NextPart_000_0061_01C5FF65.9FD7D8B0-- -- Mark Phillips Phillips Marketing, Inc [EMAIL PROTECTED] 602 524-0376 480 945-9197 fax --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
