Hi Katya, instead of returning the home page using pageWithName in your DA you could return a WORedirect pointing to it. So after login the user sees a "normal" component URL and not the DA URL.
jw Am 23.06.2010 um 21:13 schrieb Katya Yurukova: > Hi all, > > We're using a stateless login page that invokes a DA on submit. > In the DA the user input is validated, a new session is created by calling > this.session() and the home page is returned using this.pageWirhName(...). > It works as expected and no redundant sessions are created, but there is a > slight problem once the user has logged in. > > The URL displayed in the browser's address bar points to the login DA after > redirection to the home page. At least on Firefox the request is cached, so > refreshing the page results in another invocation of the DA > and the creation of a new session. I know this could be avoided if we check > for existing session in the DA but this will work only for the case when > sessionIDs are stored in cookies. > If the sessionIDs are in the URL, however, the initial DA URL does not > contain the session id and existingSession() returns null. > > I've come up with a solution for this case, but it involves redirect with the > session ID appended to the request url and I'm not very fond of it. Another > option might be storing the session ID in a cookie and forget about all the > troubles. > > In any case, I wanted to check whether there are any other options or whether > I am missing something and I have to handle the session and the response page > in the login DA differently. > > Thanks, > Katya
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
