Because the domain of the browser is file://some-long-dir/index.html, cookies
set during the RPC call are not readable. This is because the RPC call domain
is different and JS is blocking access to those cookies.
Inter RPC calls work fine as the Browser is doing the right thing for cookies
during the RPC call, so JSessionID and any cookies set my the back end are
still intact during the next call..
This might be handled by adding a custom client side serializer that will check
headers, trap and set-cookie headers and use the GWT Cookie helper class to set
also set the cookies in the domain of the GWT app.. This would also need to
occur for any Cookies.setCookie() calls on the client side, so that they are
copied from the locl domain to the RPC domain.
-John Gentilin
Original issue reported on code.google.com by gent...@eyecatching.com on 2 May 2012 at 11:40
Original issue reported on code.google.com by
gent...@eyecatching.com
on 2 May 2012 at 11:40