https://bz.apache.org/bugzilla/show_bug.cgi?id=61360
Bug ID: 61360
Summary: http session not passed to websocket ws when before
using wss
Product: Tomcat 7
Version: 7.0.79
Hardware: PC
Status: NEW
Severity: normal
Priority: P2
Component: WebSocket
Assignee: dev@tomcat.apache.org
Reporter: michael.e...@wincor-nixdorf.com
Target Milestone: ---
Created attachment 35190
--> https://bz.apache.org/bugzilla/attachment.cgi?id=35190&action=edit
A simple webapp to reproduce the problem
Steps to reproduce the problem:
1. Setup tomcat to serve https and http
2. deploy attached directory (see README.txt inside)
3. Open Chrome or FF, request the https resource, afterwards request the http
resource. Watch the tomcat console, httpSession is reported to be null!
4. If you first request http, then https and again http, it works fine (then
http has http-session not null).
What is the expected behavior?
The httpSession object in case of http should be not null.
But every reload of the http case, the http session is null. Only if you close
and open the browser, then navigate to http, it is ok (not null).
Does this feature work correctly in other browsers?
- It works correctly in MSIE 11.
- In Firefox same problem as in Chrome.
I reported this as a bug for Chrome (#749833) but Chrome developer say it's
likely to be a Tomcat problem.
--
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
