https://issues.apache.org/bugzilla/show_bug.cgi?id=48774
Summary: DNS Aliasing breaks tomcat session management
Product: Tomcat 6
Version: unspecified
Platform: PC
OS/Version: All
Status: NEW
Severity: enhancement
Priority: P2
Component: Catalina
AssignedTo: dev@tomcat.apache.org
ReportedBy: jrop...@gmail.com
One of the big problems that comet applications encounter is the 2 connection
limit of the HTTP specification, which some browsers (eg, IE6 and IE7) adhere
strictly to. The most common approach to getting around this is DNS aliasing,
where a wildcard DNS record causing all requests for all subdomains of a host
to go to that host. However, there is no way to configure what domain the
JSESSIONID gets set on, which is always set to the incoming host name. This
completely breaks Tomcat session management when DNS aliasing is being used.
If tomcat is to support comet (which it does), this seems like a pretty major
hole in its support of it, considering most comet implementations use DNS
aliasing.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
