tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From gl...@apache.org
Subject cvs commit: jakarta-tomcat-4.0/webapps/tomcat-docs proxy-howto.xml
Date Wed, 26 Nov 2003 03:42:37 GMT
glenn       2003/11/25 19:42:37

  Modified:    webapps/tomcat-docs proxy-howto.xml
  Log:
  Replace references to mod_webapp with mod_jk, add Apache 2 mod_proxy section
  
  Revision  Changes    Path
  1.4       +13 -7     jakarta-tomcat-4.0/webapps/tomcat-docs/proxy-howto.xml
  
  Index: proxy-howto.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-tomcat-4.0/webapps/tomcat-docs/proxy-howto.xml,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- proxy-howto.xml	12 Jan 2003 17:26:46 -0000	1.3
  +++ proxy-howto.xml	26 Nov 2003 03:42:37 -0000	1.4
  @@ -19,7 +19,7 @@
   <p>Using standard configurations of Tomcat, web applications can ask for
   the server name and port number to which the request was directed for
   processing.  When Tomcat is running standalone with the
  -<a href="config/http11.html">HTTP/1.1 Connector</a>, it will generally
  +<a href="config/coyote.html">Coyote HTTP/1.1 Connector</a>, it will generally
   report the server name specified in the request, and the port number on
   which the <strong>Connector</strong> is listening.  The two servlet API
   calls of interest, for this purpose, are:</p>
  @@ -47,7 +47,7 @@
   <p>Apache 1.3 supports an optional module (<code>mod_proxy</code>) that
   configures the web server to act as a proxy server.  This can be used to
   forward requests for a particular web application to a Tomcat 4 instance,
  -without having to configure a web connector such as <code>mod_webapp</code>.
  +without having to configure a web connector such as <code>mod_jk</code>.
   To accomplish this, you need to perform the following tasks:</p>
   <ol>
   <li>Configure your copy of Apache so that it includes the
  @@ -116,12 +116,18 @@
   
   <p>When requests are proxied in this manner, <strong>all</strong> requests
   for the configured web applications will be processed by Tomcat (including
  -requests for static content).  You will often be able to improve performance
  -by using the <code>mod_webapp</code> web connector instead, which
  -automatically configures itself to have Apache handle static content that is
  -not processed by filters or security constraints defined within the web
  -application's deployment descriptor (<code>/WEB-INF/web.xml</code>).</p>
  +requests for static content).  You can improve performance by using the
  +<code>mod_jk</code> web connector instead of <code>mod_proxy</code>.

  +<code>mod_jk</code> can be configured so that the web server serves static
  +content that is not processed by filters or security constraints defined
  +within the web application's deployment descriptor
  +(<code>/WEB-INF/web.xml</code>).</p>
   
  +</section>
  +
  +<section name="Apache 2.0 Proxy Support">
  +The same instructions hold true as for 1.3. (Except in Apache 2.0,
  +you may omit <code>AddModule  mod_proxy.c</code>)
   </section>
   
   </body>
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Mime
View raw message