OK, what I meant was, You have your gwt app at http://somehost/gwtapp
Now when you want to logged in the user using ssl, you will have to XHR to some https url right, https://somehost:443/gwtapp and this won't be possible as per SOP now if you load your application using https://somehost:443/gwtapp, then it will work, but I will have to forcibly use https for all the further communication, because I cant do XHR to http because of SOP. Regards, Abdullah On Tue, Feb 2, 2010 at 4:18 PM, Lothar Kimmeringer <[email protected]>wrote: > Abdullah Shaikh schrieb: > > What about SOP, I mean if you use https on the login page then how to > > proceed to the other pages after login ? > > Pass a session-token as answer to the login and use that when > accessing the server again. > > > I mean after login all the > > other pages would have to be on https right ? > > Not necessarily but not a wrong thing in dependence of the > application in question anyway. > > > Regards, Lothar > > -- > 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]<google-web-toolkit%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > > -- 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.
