If the page and the iframe content does not originate from the same server the browser security settings can cause the cookies are not accepted. For example on firefox setting "Preferences/Privacy/Cookies/ for the originating site only" should not be set.
If the cookie is set, the Cookie-header is sent on every request going to the server and you should see it on Paros. Janne On 28.8.2006, at 11.46, Nino Wael wrote: > Our problem is that every time you hit the refresh, wicket > apparently looses track of session. And creates a new sessionid. > > > The above is not so critical in it self, yet. But we have to create > authentication, so the user can login if user wants to. I've tested > the above with a simple html page on my laptop linking directly to > our base page without being mounted or having parameters encapsuled > in the url, this if working just fine. > > So im thinking that it could either be the way that the other > vendor generates the iframe to wicket that causes this or it might > be the encapsulation of parameters that does it or a combination? > > > > regards Nino > > > -----Oprindelig meddelelse----- > Fra: [EMAIL PROTECTED] på vegne af Janne > Hietamäki > Sendt: ma 28-08-2006 10:34 > Til: wicket-user@lists.sourceforge.net > Cc: > Emne: Re: [Wicket-user] Session management > > > > What kind of problems do you really have? May be you should check > this http://www.wicket-wiki.org.uk/wiki/index.php/Using_frames > > Janne > > On 28.8.2006, at 11.23, Nino Wael wrote: > > > Ahh, wasnt sure if you used something special. > > > > We use both mounted urls and url parameters, im wondering if > this > could give us the problem so for example we could have a link like > this: > > > > http://Server/viewer/overblik/Y03 > > > > where this is the raw page http://server/viewer and parameters > are overblik and Y03. the whole lot are set as the source of the > IFRAME, could any of this break the session id? > > > > Regards Nino > > > > > _____ > > > From: [EMAIL PROTECTED] [mailto:wicket- > [EMAIL PROTECTED] On Behalf Of Janne Hietamäki > Sent: 28. august 2006 10:06 > To: wicket-user@lists.sourceforge.net > Subject: Re: [Wicket-user] Session management > > > > Session cookie expires when browser is shut down, but on the > server side the default is 30 minutes. This can be altered in the > web.xml by adding something like this: > > > > > > <session-config> > > <session-timeout>60</session-timeout> > > </session-config> > > > > > > Janne > > > > On 28.8.2006, at 11.00, Nino Wael wrote: > > > > > > That was what I thought, I do know that wicket is not the bad > guy > here:-) > > > > Whats the default timeout on the cookie? Or am I barking up the > > wrong leg? > > > > .regards Nino ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
