Pete,
this is a fairly common limitation with setting cookies, as it is difficult
for a container to tell what the domain actually is to set - specially
if multiple ports and/or virtual hosts are involved.
However, in the 4.1.0 release of Jetty, just gone out the door and
coming to a JBoss rele
I think I may have discovered a nasty bug in Jetty's cookie based
session management.
I'm using version JBoss 3.0.2 and Mozilla 1.0 and here's the problem I'm
encountering.
When jetty creates a cookie for a session (named jsessionid) it doesn't
set the domain that it applies to. This results in
