Closed GoogleCodeExporter closed 9 years ago
I was able to reproduce if i go to the glassfish admin console (localhost:4848)
then WebPasswordSafe (localhost:8080). It appears glassfish creates two
JSESSIONIDs, one for / path (port 4848) and one for /WebPasswordSafe (port
8080) and the browser sends both of them to WebPasswordSafe confusing it as to
which to use for CSRF protection. Need to see if GWT can retrieve cookies
based on path. Instead of the code change above, an alternative workaround
would be a config file change to set all "strongCsrfProtection" values in
war/WEB-INF/rpc-servlet.xml to "false"
Original comment by joshdrum...@gmail.com
on 10 Dec 2010 at 4:40
Decoupled CSRF cookie from JSESSIONID to be application specific to avoid
conflicts with other applications such as with Glassfish
Original comment by joshdrum...@gmail.com
on 10 Dec 2010 at 9:41
works fine thanks!
Original comment by m...@shofer.ch
on 11 Dec 2010 at 11:09
Original issue reported on code.google.com by
m...@shofer.ch
on 9 Dec 2010 at 6:40