Also look out for requests to http://www.yoursiteurl.com and http://yoursiteurl.com
Cookies for one, depending on the way your cookies are being set (the host, in particular), may not be valid for both. On Oct 12, 5:14 am, George Georgovassilis <[email protected]> wrote: > Hello Denis, > > That is unlikely - cookie values are mostly set on the server side. > Since you are using Firebug, why don't you look out for the one > response that overrides the cookie? JSP pages for instance like > setting their own cookies in the default setup. Another thing to watch > for is the cookie path set by the server. A cookie set > athttp://localhost:8080/myappis not the same cookie as the one set > athttp://localhost:8080/myapp/services/login.rpcbecause the browser > stores the path together with the cookie name. > > On Oct 11, 7:47 pm, denis56 <[email protected]> wrote: > > > His to everyone, > > > We are experiencing a wicked behavior on the web page that uses one > > GWT component running regular updates. Maybe someone could provide an > > insight. > > > The thing is that after a couple of PRC requests you can see in > > Firebug that the sessionid sent to client on previous response does > > not correspond to the sessionid that is sent on subsequent PRC > > request. As a side effect users get wrong session cookie and resulting > > in unintended log outs. Really strange and happens only irregularly. > > > On of the suspicions is that GWT might internally manipulate sessions > > (we are using GWT 2.0) because no cookies are set by us explicitly? > > > Thanks. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
