Hietamäki
Sent: 28. august 2006 13:17
To: wicket-user@lists.sourceforge.net
Subject: Re: [Wicket-user] Session management
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
ts.sourceforge.net
> Betreff: Re: [Wicket-user] Session management
>
> I see the problem, as a default firefox actually allows 3rd
> party cookies. But we are targeting IE 6(SP2) which does not
> by default allow 3rd party cookies.
>
> Thanks for your mail.
>
> Regard
gt; -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
>
>
>
@lists.sourceforge.net
Subject: Re: [Wicket-user] Session
management
Im using Paros, trying out the plugin for firefox.
But as far as I can see
Wicket asks to set a new
session(initial page):
http://img181.imageshack.us/my.php?image=session1pq3.jpg
second hit
/session2vh3.jpg
regards Nino
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Johan Compagner
Sent: 28. august 2006 10:49
To: wicket-user@lists.sourceforge.net
Subject: Re: [Wicket-user] Session
management
you could use the FireFox
plugin
L PROTECTED] på vegne af Janne HietamäkiSendt: ma 28-08-2006 10:34
Til: wicket-user@lists.sourceforge.netCc:Emne: Re: [Wicket-user] Session managementWhat kind of problems do you really have? May be you should check this
http://www.wicket-wiki.org.uk/wik
ECTED] [mailto:[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
: [EMAIL PROTECTED] [mailto:[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
: 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:
60
Janne
On 28.8.2006, at
default timeout on the cookie? Or am I barking up the wrong leg? .regards Nino From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Janne Hietamäki Sent: 28. august 2006 09:56 To: wicket-user@lists.sourceforge.net Subject: Re: [Wicket-user] Session management On 28.8.2006, at 10.53
To:
wicket-user@lists.sourceforge.net
Subject: Re: [Wicket-user] Session
management
On 28.8.2006, at 10.53, Nino Wael wrote:
Hi
I
was wondering how wicket maintains it’s session state. We are currently working
on a crossbrowser application, where our application(wicket
On 28.8.2006, at 10.53, Nino Wael wrote: Hi I was wondering how wicket maintains it’s session state. We are currently working on a crossbrowser application, where our application(wicket) lives within an Iframe. If we hit refresh on the page, wicket looses its session id. As far as I can see wicket
Hi
I was wondering how wicket maintains it’s
session state. We are currently working on a crossbrowser application, where
our application(wicket) lives within an Iframe. If we hit refresh on the page,
wicket looses its session id. As far as I can see wicket does store the session
id in
any kind of verification you want. thats your business logic. you have access to the session so you can pull the user from that.-IgorOn 11/26/05,
Manuel Corrales <[EMAIL PROTECTED]> wrote:
Ok, this worked ok. Now i have a question, what kind of verification
should i do on checkAccess(), and if i i
Ok, this worked ok. Now i have a question, what kind of verification
should i do on checkAccess(), and if i inherits AuthenticatedWebPage,
what that do to my pages??
Looks right-IgorOn 11/22/05, Manuel Corrales <[EMAIL PROTECTED]> wrote:
I have this session:
public final class UserSession extends WebSession
{
private Usuario user;
/**
* Constructor.
* @param app
*/
public UserSession(Application app)
{
super(app);
I have this session:
public final class UserSession extends WebSession
{
private Usuario user;
/**
* Constructor.
* @param app
*/
public UserSession(Application app)
{
super(app);
}
/**
*
* @return true si existe un usuario logead
On 11/21/05, Manuel Corrales <[EMAIL PROTECTED]> wrote:
Hi, i've asked this question once but dont get a solution. So here i go again:Sorry, must've missed it.
I have some clues about stateful beans and stateless beans but not too
much. What i need is that when a user logins, create an object and
You could best take a look at the sign-in example of wicket-examples.
It has a custom session - which can be used to store information you
want to keep during the whole user session - and it has an example of
how to prevent access/ redirect to a login page for a non logged on
user.
Eelco
On 11/2
Hi, i've asked this question once but dont get a solution. So here i go again:
I have some clues about stateful beans and stateless beans but not too
much. What i need is that when a user logins, create an object and that
that object exists during the user session (to logout). Now i think
this is
That is not a matter of Wicket (Struts, Webwork). You have to
configure the servlet container (jetty, tomcat, etc)
Juergen
On 8/7/05, David Liebeherr <[EMAIL PROTECTED]> wrote:
> Hi all!
>
> How can i set wicket to only use URL-Rewriting for sessions rather than
> cookies no matter if the
> bro
Hi all!
How can i set wicket to only use URL-Rewriting for sessions rather than cookies no matter if the
browser supports cookies or not?
Thanx,
Dave
---
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 20
22 matches
Mail list logo
