Hi Leif and thanks a lot for your advise.
I tried to watch the cookies as you recommended. So here is what I’ve got form after browser refresh.
Firefox:
Response Headers
HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Cache-Control: no-cache
Pragma: no-cache
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Content-Type: text/html;charset=UTF-8
Content-Length: 2604
Date: Mon, 12 Mar 2012 16:36:16 GMT
Request Headers
GET /AddressBook HTTP/1.1
Host: localhost:8080
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20100101 Firefox/10.0.2
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip, deflate
Connection: keep-alive
Cookie: JSESSIONID=110959AF86DFC4A4DB839DCE5329509F
Cache-Control: max-age=0
Response Headers
HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Content-Type: text/html
Transfer-Encoding: chunked
Date: Mon, 12 Mar 2012 16:36:16 GMT
Request Headers
GET /AddressBook/VAADIN/widgetsets/com.vaadin.terminal.gwt.DefaultWidgetSet/516172B066DA8C0C150C685E3318393D.cache.html HTTP/1.1
Host: localhost:8080
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20100101 Firefox/10.0.2
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip, deflate
Connection: keep-alive
Referer: http://localhost:8080/AddressBook
Cookie: JSESSIONID=110959AF86DFC4A4DB839DCE5329509F
Chrome:
Request Headers
GET /AddressBook/VAADIN/themes/runo/table/img/resizer-bg.png HTTP/1.1
Host: localhost:8080
Connection: keep-alive
Cache-Control: max-age=0
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.11 (KHTML, like Gecko) Chrome/17.0.963.78 Safari/535.11
Accept: */*
Referer: http://localhost:8080/AddressBook
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: JSESSIONID=2CD3536D410CCC7AA8B11EAF97C3D3EE
Response Headers
HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Content-Type: image/png
Content-Length: 141
Date: Mon, 12 Mar 2012 17:01:38 GMT
Request Headers
GET /AddressBook/VAADIN/themes/runo/table/img/resizer-bg.png HTTP/1.1
Host: localhost:8080
Connection: keep-alive
Cache-Control: max-age=0
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.11 (KHTML, like Gecko) Chrome/17.0.963.78 Safari/535.11
Accept: */*
Referer: http://localhost:8080/AddressBook
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: JSESSIONID=50BADEB964E165E98C0B128E2162FED7
Response Headers
HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Content-Type: image/png
Content-Length: 141
Date: Mon, 12 Mar 2012 17:02:40 GMT
Well, I can’t see a fundamental difference between the headers in Chrome and Firefox, except that Firefox continue using the same session (JSESSIONID=110959AF86DFC4A4DB839DCE5329509F) after page refresh, while Chrome gets a new session (JSESSIONID=50BADEB964E165E98C0B128E2162FED7 vs JSESSIONID=2CD3536D410CCC7AA8B11EAF97C3D3EE).
Tomcat’s Session Administration page just confirms this: new session has been thrown for application on Chrome and the same session remains for Firefox.
Any comments are very welcome…