Session id and cookie #30
Description
I have a working setup for my GWT application which, on login, generates a
session id (UUID), stores it in the HTTPSession and returns it to the client.
The actual GWT client saves this session id as a Cookie and sends it as a
parameter with each request (the cookie is send automatically as well).
So the server will receive the client id three times (HTTPSession, Cookie and
parameter).
On the Android client I'm developing, when sending the second request (after
receiving the session id), the only session id (out of the three) that reaches
the server is the one send as a parameter. So the cookie session id and the
actual session id (in the HTTPSession) are null on the server side.
What steps will reproduce the problem?
1. First RPC generates session id and returns to client
2. Store session id in current HTTPSession on server
3. Store session id in CookieManager on client
4. Next RPC call sends session id as parameter to server using the same
CookieManager
5. Only the parameter reaches the server.
What is the expected output? What do you see instead?
Receiving all three session ids on the server side (or at least more than the
one that is currently received). Server only receives the parameter
What version of the product are you using? On what operating system?
SyncProxyAndroid-0.4. Client runs Android 4.2.2.
Please provide any additional information below.
Original issue reported on code.google.com by S.Raub...@web.de on 26 Sep 2013 at 12:57