https://issues.apache.org/bugzilla/show_bug.cgi?id=55824
--- Comment #5 from Mark Thomas <ma...@apache.org> --- That isn't how I read it. If there is no "HTTP session under which a client is operating" then there is no requirement to create one. If you want an HTTP session to be available then you'll have to create one first (e.g. with a filter). Note that the lifecycle of the HTTP session is separate from that of the WebSocket session and the HTTP session can timeout irrespective of whether or not the WebSocket session is still active. "Anyway, it's quite inconvenient to have to create something else, a dummy, that creates the HttpSession, just to get at the container's context, and thus, parameters needed to configure the websocket." suggests you aren't configuring your WebSocket connections correctly. There should be no need for access to the HTTP session to do this. The users list is the place to follow up on that. -- 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
