|Summary:||DNS Aliasing breaks tomcat session management|
|Product:||Tomcat 6||Reporter:||James Roper <jroper2>|
|Component:||Catalina||Assignee:||Tomcat Developers Mailing List <dev>|
Description James Roper 2010-02-19 05:32:32 UTC
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.