http://git-wip-us.apache.org/repos/asf/flex-blazeds/blob/5be16a28/attic/servers/apache-tomcat-6.0.29/webapps/docs/proxy-howto.html
----------------------------------------------------------------------
diff --git a/attic/servers/apache-tomcat-6.0.29/webapps/docs/proxy-howto.html 
b/attic/servers/apache-tomcat-6.0.29/webapps/docs/proxy-howto.html
new file mode 100644
index 0000000..fe94a00
--- /dev/null
+++ b/attic/servers/apache-tomcat-6.0.29/webapps/docs/proxy-howto.html
@@ -0,0 +1,121 @@
+<html><head><META http-equiv="Content-Type" content="text/html; 
charset=iso-8859-1"><title>Apache Tomcat 6.0 - Proxy Support 
HOW-TO</title><meta content="Craig R. McClanahan" name="author"><style 
media="print" type="text/css">
+                       .noPrint {display: none;}
+                       td#mainBody {width: 100%;}
+               </style></head><body vlink="#525D76" alink="#525D76" 
link="#525D76" text="#000000" bgcolor="#ffffff"><table cellspacing="0" 
width="100%" border="0"><!--PAGE HEADER--><tr><td><!--PROJECT LOGO--><a 
href="http://tomcat.apache.org/";><img border="0" alt="
+      The Apache Tomcat Servlet/JSP Container
+    " align="right" src="./images/tomcat.gif"></a></td><td><h1><font 
face="arial,helvetica,sanserif">Apache Tomcat 
6.0</font></h1></td><td><!--APACHE LOGO--><a href="http://www.apache.org/";><img 
border="0" alt="Apache Logo" align="right" 
src="./images/asf-logo.gif"></a></td></tr></table><table cellspacing="4" 
width="100%" border="0"><!--HEADER SEPARATOR--><tr><td colspan="2"><hr size="1" 
noshade></td></tr><tr><!--LEFT SIDE NAVIGATION--><td class="noPrint" nowrap 
valign="top" width="20%"><p><strong>Links</strong></p><ul><li><a 
href="index.html">Docs Home</a></li><li><a 
href="http://wiki.apache.org/tomcat/FAQ";>FAQ</a></li></ul><p><strong>User 
Guide</strong></p><ul><li><a href="introduction.html">1) 
Introduction</a></li><li><a href="setup.html">2) Setup</a></li><li><a 
href="appdev/index.html">3) First webapp</a></li><li><a 
href="deployer-howto.html">4) Deployer</a></li><li><a 
href="manager-howto.html">5) Manager</a></li><li><a href="realm-howto.html">6) 
Realms and AAA</a></li><li><a hr
 ef="security-manager-howto.html">7) Security Manager</a></li><li><a 
href="jndi-resources-howto.html">8) JNDI Resources</a></li><li><a 
href="jndi-datasource-examples-howto.html">9) JDBC DataSources</a></li><li><a 
href="class-loader-howto.html">10) Classloading</a></li><li><a 
href="jasper-howto.html">11) JSPs</a></li><li><a href="ssl-howto.html">12) 
SSL</a></li><li><a href="ssi-howto.html">13) SSI</a></li><li><a 
href="cgi-howto.html">14) CGI</a></li><li><a href="proxy-howto.html">15) Proxy 
Support</a></li><li><a href="mbeans-descriptor-howto.html">16) MBean 
Descriptor</a></li><li><a href="default-servlet.html">17) Default 
Servlet</a></li><li><a href="cluster-howto.html">18) Clustering</a></li><li><a 
href="balancer-howto.html">19) Load Balancer</a></li><li><a 
href="connectors.html">20) Connectors</a></li><li><a href="monitoring.html">21) 
Monitoring and Management</a></li><li><a href="logging.html">22) 
Logging</a></li><li><a href="apr.html">23) APR/Native</a></li><li><a 
href="virtual-ho
 sting-howto.html">24) Virtual Hosting</a></li><li><a href="aio.html">25) 
Advanced IO</a></li><li><a href="extras.html">26) Additional 
Components</a></li><li><a href="maven-jars.html">27) 
Mavenized</a></li></ul><p><strong>Reference</strong></p><ul><li><a 
href="RELEASE-NOTES.txt">Release Notes</a></li><li><a 
href="config/index.html">Configuration</a></li><li><a 
href="api/index.html">Javadocs</a></li><li><a 
href="http://tomcat.apache.org/connectors-doc/";>JK 1.2 
Documentation</a></li></ul><p><strong>Apache Tomcat 
Development</strong></p><ul><li><a href="building.html">Building</a></li><li><a 
href="changelog.html">Changelog</a></li><li><a 
href="http://wiki.apache.org/tomcat/TomcatVersions";>Status</a></li><li><a 
href="developers.html">Developers</a></li><li><a 
href="architecture/index.html">Architecture</a></li><li><a 
href="funcspecs/index.html">Functional Specs.</a></li></ul></td><!--RIGHT SIDE 
MAIN BODY--><td id="mainBody" align="left" valign="top" width="80%"><h1>Apache 
Tomcat 6.0</h1>
 <h2>Proxy Support HOW-TO</h2><table cellpadding="2" cellspacing="0" 
border="0"><tr><td bgcolor="#525D76"><font face="arial,helvetica.sanserif" 
color="#ffffff"><a name="Table of Contents"><!--()--></a><a 
name="Table_of_Contents"><strong>Table of 
Contents</strong></a></font></td></tr><tr><td><blockquote>
+<ul><li><a href="#Introduction">Introduction</a></li><li><a 
href="#Apache_1.3_Proxy_Support">Apache 1.3 Proxy Support</a></li><li><a 
href="#Apache_2.0_Proxy_Support">Apache 2.0 Proxy Support</a></li></ul>
+</blockquote></td></tr></table><table cellpadding="2" cellspacing="0" 
border="0"><tr><td bgcolor="#525D76"><font face="arial,helvetica.sanserif" 
color="#ffffff"><a 
name="Introduction"><strong>Introduction</strong></a></font></td></tr><tr><td><blockquote>
+
+<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/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 servlet API
+calls of interest, for this purpose, are:</p>
+<ul>
+<li><code>ServletRequest.getServerName()</code>: Returns the host name of the 
server to which the request was sent.</li>
+<li><code>ServletRequest.getServerPort()</code>: Returns the host name of the 
server to which the request was sent.</li>
+<li><code>ServletRequest.getLocalName()</code>: Returns the host name of the 
Internet Protocol (IP) interface on which the request was received.</li>
+<li><code>ServletRequest.getLocalPort()</code>:  Returns the Internet Protocol 
(IP) port number of the interface on which the request was received.</li>
+</ul>
+
+<p>When you are running behind a proxy server (or a web server that is
+configured to behave like a proxy server), you will sometimes prefer to
+manage the values returned by these calls.  In particular, you will
+generally want the port number to reflect that specified in the original
+request, not the one on which the <strong>Connector</strong> itself is
+listening.  You can use the <code>proxyName</code> and <code>proxyPort</code>
+attributes on the <code>&lt;Connector&gt;</code> element to configure
+these values.</p>
+
+<p>Proxy support can take many forms.  The following sections describe
+proxy configurations for several common cases.</p>
+
+</blockquote></td></tr></table><table cellpadding="2" cellspacing="0" 
border="0"><tr><td bgcolor="#525D76"><font face="arial,helvetica.sanserif" 
color="#ffffff"><a name="Apache 1.3 Proxy Support"><!--()--></a><a 
name="Apache_1.3_Proxy_Support"><strong>Apache 1.3 Proxy 
Support</strong></a></font></td></tr><tr><td><blockquote>
+
+<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 6 instance,
+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
+    <code>mod_proxy</code> module.  If you are building from source,
+    the easiest way to do this is to include the
+    <code>--enable-module=proxy</code> directive on the
+    <code>./configure</code> command line.</li>
+<li>If not already added for you, make sure that you are loading the
+    <code>mod_proxy</code> module at Apache startup time, by using the
+    following directives in your <code>httpd.conf</code> file:
+<div align="left"><table border="0" cellpadding="0" cellspacing="4"><tr><td 
height="1" width="1" bgcolor="#023264"><img border="0" hspace="0" vspace="0" 
height="1" width="1" alt="" src="./images/void.gif"></td><td height="1" 
bgcolor="#023264"><img border="0" hspace="0" vspace="0" height="1" width="1" 
alt="" src="./images/void.gif"></td><td height="1" width="1" 
bgcolor="#023264"><img border="0" hspace="0" vspace="0" height="1" width="1" 
alt="" src="./images/void.gif"></td></tr><tr><td width="1" 
bgcolor="#023264"><img border="0" hspace="0" vspace="0" height="1" width="1" 
alt="" src="./images/void.gif"></td><td height="1" bgcolor="#ffffff"><pre>
+LoadModule proxy_module  {path-to-modules}/mod_proxy.so
+AddModule  mod_proxy.c
+</pre></td><td width="1" bgcolor="#023264"><img border="0" hspace="0" 
vspace="0" height="1" width="1" alt="" 
src="./images/void.gif"></td></tr><tr><td height="1" width="1" 
bgcolor="#023264"><img border="0" hspace="0" vspace="0" height="1" width="1" 
alt="" src="./images/void.gif"></td><td height="1" bgcolor="#023264"><img 
border="0" hspace="0" vspace="0" height="1" width="1" alt="" 
src="./images/void.gif"></td><td height="1" width="1" bgcolor="#023264"><img 
border="0" hspace="0" vspace="0" height="1" width="1" alt="" 
src="./images/void.gif"></td></tr></table></div></li>
+<li>Include two directives in your <code>httpd.conf</code> file for
+    each web application that you wish to forward to Tomcat 6.  For
+    example, to forward an application at context path <code>/myapp</code>:
+<div align="left"><table border="0" cellpadding="0" cellspacing="4"><tr><td 
height="1" width="1" bgcolor="#023264"><img border="0" hspace="0" vspace="0" 
height="1" width="1" alt="" src="./images/void.gif"></td><td height="1" 
bgcolor="#023264"><img border="0" hspace="0" vspace="0" height="1" width="1" 
alt="" src="./images/void.gif"></td><td height="1" width="1" 
bgcolor="#023264"><img border="0" hspace="0" vspace="0" height="1" width="1" 
alt="" src="./images/void.gif"></td></tr><tr><td width="1" 
bgcolor="#023264"><img border="0" hspace="0" vspace="0" height="1" width="1" 
alt="" src="./images/void.gif"></td><td height="1" bgcolor="#ffffff"><pre>
+ProxyPass         /myapp  http://localhost:8081/myapp
+ProxyPassReverse  /myapp  http://localhost:8081/myapp
+</pre></td><td width="1" bgcolor="#023264"><img border="0" hspace="0" 
vspace="0" height="1" width="1" alt="" 
src="./images/void.gif"></td></tr><tr><td height="1" width="1" 
bgcolor="#023264"><img border="0" hspace="0" vspace="0" height="1" width="1" 
alt="" src="./images/void.gif"></td><td height="1" bgcolor="#023264"><img 
border="0" hspace="0" vspace="0" height="1" width="1" alt="" 
src="./images/void.gif"></td><td height="1" width="1" bgcolor="#023264"><img 
border="0" hspace="0" vspace="0" height="1" width="1" alt="" 
src="./images/void.gif"></td></tr></table></div>
+    which tells Apache to forward URLs of the form
+    <code>http://localhost/myapp/*</code> to the Tomcat 6 connector
+    listening on port 8081.</li>
+<li>Configure your copy of Tomcat 6 to include a special
+    <code>&lt;Connector&gt;</code> element, with appropriate
+    proxy settings, for example:
+<div align="left"><table border="0" cellpadding="0" cellspacing="4"><tr><td 
height="1" width="1" bgcolor="#023264"><img border="0" hspace="0" vspace="0" 
height="1" width="1" alt="" src="./images/void.gif"></td><td height="1" 
bgcolor="#023264"><img border="0" hspace="0" vspace="0" height="1" width="1" 
alt="" src="./images/void.gif"></td><td height="1" width="1" 
bgcolor="#023264"><img border="0" hspace="0" vspace="0" height="1" width="1" 
alt="" src="./images/void.gif"></td></tr><tr><td width="1" 
bgcolor="#023264"><img border="0" hspace="0" vspace="0" height="1" width="1" 
alt="" src="./images/void.gif"></td><td height="1" bgcolor="#ffffff"><pre>
+&lt;Connector port="8081" ...
+              proxyName="www.mycompany.com"
+              proxyPort="80"/&gt;
+</pre></td><td width="1" bgcolor="#023264"><img border="0" hspace="0" 
vspace="0" height="1" width="1" alt="" 
src="./images/void.gif"></td></tr><tr><td height="1" width="1" 
bgcolor="#023264"><img border="0" hspace="0" vspace="0" height="1" width="1" 
alt="" src="./images/void.gif"></td><td height="1" bgcolor="#023264"><img 
border="0" hspace="0" vspace="0" height="1" width="1" alt="" 
src="./images/void.gif"></td><td height="1" width="1" bgcolor="#023264"><img 
border="0" hspace="0" vspace="0" height="1" width="1" alt="" 
src="./images/void.gif"></td></tr></table></div>
+    which will cause servlets inside this web application to think that
+    all proxied requests were directed to <code>www.mycompany.com</code>
+    on port 80.</li>
+<li>It is legal to omit the <code>proxyName</code> attribute from the
+    <code>&lt;Connector&gt;</code> element.  If you do so, the value
+    returned by <code>request.getServerName()</code> will by the host
+    name on which Tomcat is running.  In the example above, it would be
+    <code>localhost</code>.</li>
+<li>If you also have a <code>&lt;Connector&gt;</code> listening on port
+    8080 (nested within the same <a href="config/service.html">Service</a>
+    element), the requests to either port will share the same set of
+    virtual hosts and web applications.</li>
+<li>You might wish to use the IP filtering features of your operating
+    system to restrict connections to port 8081 (in this example) to
+    be allowed <strong>only</strong> from the server that is running
+    Apache.</li>
+<li>Alternatively, you can set up a series of web applications that are
+    only available via proxying, as follows:
+    <ul>
+    <li>Configure another <code>&lt;Service&gt;</code> that contains
+        only a <code>&lt;Connector&gt;</code> for the proxy port.</li>
+    <li>Configure appropriate <a href="config/engine.html">Engine</a>,
+        <a href="config/host.html">Host</a>, and
+        <a href="config/context.html">Context</a> elements for the virtual 
hosts
+        and web applications accessible via proxying.</li>
+    <li>Optionally, protect port 8081 with IP filters as described
+        earlier.</li>
+    </ul></li>
+<li>When requests are proxied by Apache, the web server will be recording
+    these requests in its access log.  Therefore, you will generally want to
+    disable any access logging performed by Tomcat itself.</li>
+</ol>
+
+<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 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>
+
+</blockquote></td></tr></table><table cellpadding="2" cellspacing="0" 
border="0"><tr><td bgcolor="#525D76"><font face="arial,helvetica.sanserif" 
color="#ffffff"><a name="Apache 2.0 Proxy Support"><!--()--></a><a 
name="Apache_2.0_Proxy_Support"><strong>Apache 2.0 Proxy 
Support</strong></a></font></td></tr><tr><td><blockquote>
+The same instructions hold true as for 1.3. (Except in Apache 2.0,
+you may omit <code>AddModule  mod_proxy.c</code>)
+</blockquote></td></tr></table></td></tr><!--FOOTER SEPARATOR--><tr><td 
colspan="2"><hr size="1" noshade></td></tr><!--PAGE FOOTER--><tr><td 
colspan="2"><div align="center"><font size="-1" color="#525D76"><em>
+        Copyright &copy; 1999-2010, Apache Software Foundation
+        </em></font></div></td></tr></table></body></html>
\ No newline at end of file

Reply via email to