tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 34648] New: - AJP uses Host header not ServerName directive from Apache
Date Wed, 27 Apr 2005 15:12:36 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=34648>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=34648

           Summary: AJP uses Host header not ServerName directive from
                    Apache
           Product: Tomcat 5
           Version: Unknown
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P3
         Component: Connector:AJP
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: dhopper@bzresults.com


Currently the implementation for which AJP1/3 Connector selects which host to
pass the request to is determined solely by the HTTP Host header.  It would be
nice if it could optionally use the ServerName directive that is passed from
Apache through mod_jk to the AJP1/3 Connector.  This would be create for ISP
hosting enviroments in which name based hosting may not always be the hosting
method.  Currently our setup we have some hosts that are name based and some
that are address based.  For address based hosts consider the following apache conf

<VirtualHost 192.168.2.100>
ServerName www.testhost.com
JkMount /* default
</VirtualHost>

and the associated tomcat host conf

<Host name="testhost" appBase="webapps">
  <Alias>www.testhost.com</Alias>
</Host>

Now this client is setup as and address based host.  Let also say that the
domain name www.testhost2.com resolves to 192.168.2.100 as well.  Since we don't
always manage the DNS and clients could have (N) domains pointing to their IP
address.  The domain www.testhost.com will work just fine but www.testhost2.com
will not, b/c the host header will have www.testhost2.com obviously instead of
www.testhost.com.  Now if tomcat had an option to use the ServerName directive
if it was passed this would then work for both the domains in question, as it
would lookup of www.testhost.com from ServerName passed through mod_jk instead
of just solely looking up the Host Header.

This obviously isn't a bug but a feature request, I know that other containers
do already do this like Resin, handles this situation just fine.

Tomcat Version: 5.5.9
Mod_JK: 1.2.10
Apache: 2.0.54

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
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