[
http://jira.jboss.com/jira/browse/JBWEB-17?page=all ]
Remy Maucherat resolved JBWEB-17.
---------------------------------
Resolution: Rejected
The Tomcat architecture uses a hierachical view that is good for many things, including
sensible configurability, but in return is not as flexible for mixing and matching
connectors with hosts and individual webapps.
Options include access restriction valves or "URL" rewriting using the JBoss Web
rewrite valve, which will provide something transparent to your webapp.
support mapping multiple Connectors to different vhosts
-------------------------------------------------------
Key: JBWEB-17
URL:
http://jira.jboss.com/jira/browse/JBWEB-17
Project: JBoss Web
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Tomcat Module
Reporter: Jan Hecking
Assigned To: Remy Maucherat
See forum posting:
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870728
I'd like to deploy several web apps in a single JBoss server. Some of these apps are
for internal use only. For security reasons it is required that the internal apps are not
available on the same port as the external apps. Using regular vhosts is not sufficient as
the vhost being accessed entirely depends on the Host: HTTP header sent by the client so
requests to the "internal" vhosts cannot be blocked by the firewall on the
TCP/IP layer but only by analyzing the HTTP request on the application layer.
As Scott Stark suggested in a reply to my forum posting it would be great if different
Tomcat HTTP Connectors could be mapped to each vhost.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira