You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Erik van Oosten <e....@grons.nl> on 2009/08/02 19:16:29 UTC
Re: Stateless login form?
Martin,
I am not sure what you mean. On the site you are referring, the login
page is always visible under /login.
Regards,
Erik.
Martin Makundi wrote:
>> If I understood correctly, you might find this interesting:
>> http://day-to-day-stuff.blogspot.com/2008/10/wicket-extreme-consistent-urls.html
>>
>
> Does appear to make stateless-looking urls AFTER you CLICK/REDIRECT
> (looking at the example page referred on the site). Not BEFORE you
> CLICK...
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Stateless login form?
Posted by Martin Makundi <ma...@koodaripalvelut.com>.
> Jeremy Thomerson already gave you the hint: override isStateless and return
> true... thus you'll not get a session relative url.
Ok. That might work, I actually get:
https://localhost/login/wicket:interface/:0:loginForm::IFormSubmitListener::;jsessionid=139rzdeu5rm09
And on a first try, it really does seem to work though it "appears"
stateful (=to an uneducated eye).
Thank you!
My next challenge is that sometimes users bookmark authenticated pages
and when they return, for some reason Wicket instantiates such pages
that require authentication though it should be prevented by specific
annotations. Instatiation results in nullpointer exceptions due to
lacking login data...
**
Martin.
>
> Alex.
>
>
>
> MartinM wrote:
>>
>> Login page is visible, but the form
>> action="/?wicket:interface=:0:1::::" which is stateful. If my session
>> dies I will definitely get an error.
>>
>> Try clicking this link with a new browser that does not have a session
>> on the site: http://www.tipspot.com/?wicket:interface=:0:1::::
>>
>> This is what you would get if your browser loaded the page from cache
>> (or if you let it wait until the session invalidates). Does not look
>> professional and it is totaly unnecessary, in my opinnion. It should
>> be possible to handle forms on "virgin" (=no state bound yet)
>> invocations too.
>>
>> **
>> Martin
>>
>> 2009/8/2 Erik van Oosten <e....@grons.nl>:
>>> Martin,
>>>
>>> I am not sure what you mean. On the site you are referring, the login
>>> page
>>> is always visible under /login.
>>>
>>> Regards,
>>> Erik.
>>>
>>> Martin Makundi wrote:
>>>>>
>>>>> If I understood correctly, you might find this interesting:
>>>>>
>>>>> http://day-to-day-stuff.blogspot.com/2008/10/wicket-extreme-consistent-urls.html
>>>>>
>>>>
>>>> Does appear to make stateless-looking urls AFTER you CLICK/REDIRECT
>>>> (looking at the example page referred on the site). Not BEFORE you
>>>> CLICK...
>>>>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>>
>
> --
> View this message in context: http://www.nabble.com/Stateless-login-form--tp24757066p24782234.html
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Stateless login form?
Posted by Alex Objelean <al...@yahoo.com>.
Jeremy Thomerson already gave you the hint: override isStateless and return
true... thus you'll not get a session relative url.
Alex.
MartinM wrote:
>
> Login page is visible, but the form
> action="/?wicket:interface=:0:1::::" which is stateful. If my session
> dies I will definitely get an error.
>
> Try clicking this link with a new browser that does not have a session
> on the site: http://www.tipspot.com/?wicket:interface=:0:1::::
>
> This is what you would get if your browser loaded the page from cache
> (or if you let it wait until the session invalidates). Does not look
> professional and it is totaly unnecessary, in my opinnion. It should
> be possible to handle forms on "virgin" (=no state bound yet)
> invocations too.
>
> **
> Martin
>
> 2009/8/2 Erik van Oosten <e....@grons.nl>:
>> Martin,
>>
>> I am not sure what you mean. On the site you are referring, the login
>> page
>> is always visible under /login.
>>
>> Regards,
>> Erik.
>>
>> Martin Makundi wrote:
>>>>
>>>> If I understood correctly, you might find this interesting:
>>>>
>>>> http://day-to-day-stuff.blogspot.com/2008/10/wicket-extreme-consistent-urls.html
>>>>
>>>
>>> Does appear to make stateless-looking urls AFTER you CLICK/REDIRECT
>>> (looking at the example page referred on the site). Not BEFORE you
>>> CLICK...
>>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/Stateless-login-form--tp24757066p24782234.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Stateless login form?
Posted by Erik van Oosten <e....@grons.nl>.
Ah, I get it. Yes, you are right too, just never got around rewriting
the login to a stateless form. It has no priority though as our session
never dies.
Regards,
Erik.
Martin Makundi wrote:
> Login page is visible, but the form
> action="/?wicket:interface=:0:1::::" which is stateful. If my session
> dies I will definitely get an error.
>
> Try clicking this link with a new browser that does not have a session
> on the site: http://www.tipspot.com/?wicket:interface=:0:1::::
>
> This is what you would get if your browser loaded the page from cache
> (or if you let it wait until the session invalidates). Does not look
> professional and it is totaly unnecessary, in my opinnion. It should
> be possible to handle forms on "virgin" (=no state bound yet)
> invocations too.
>
> **
> Martin
>
> 2009/8/2 Erik van Oosten <e....@grons.nl>:
>
>> Martin,
>>
>> I am not sure what you mean. On the site you are referring, the login page
>> is always visible under /login.
>>
>> Regards,
>> Erik.
>>
>> Martin Makundi wrote:
>>
>>>> If I understood correctly, you might find this interesting:
>>>>
>>>> http://day-to-day-stuff.blogspot.com/2008/10/wicket-extreme-consistent-urls.html
>>>>
>>>>
>>> Does appear to make stateless-looking urls AFTER you CLICK/REDIRECT
>>> (looking at the example page referred on the site). Not BEFORE you
>>> CLICK...
>>>
>>>
--
Erik van Oosten
http://day-to-day-stuff.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Stateless login form?
Posted by Martin Makundi <ma...@koodaripalvelut.com>.
Login page is visible, but the form
action="/?wicket:interface=:0:1::::" which is stateful. If my session
dies I will definitely get an error.
Try clicking this link with a new browser that does not have a session
on the site: http://www.tipspot.com/?wicket:interface=:0:1::::
This is what you would get if your browser loaded the page from cache
(or if you let it wait until the session invalidates). Does not look
professional and it is totaly unnecessary, in my opinnion. It should
be possible to handle forms on "virgin" (=no state bound yet)
invocations too.
**
Martin
2009/8/2 Erik van Oosten <e....@grons.nl>:
> Martin,
>
> I am not sure what you mean. On the site you are referring, the login page
> is always visible under /login.
>
> Regards,
> Erik.
>
> Martin Makundi wrote:
>>>
>>> If I understood correctly, you might find this interesting:
>>>
>>> http://day-to-day-stuff.blogspot.com/2008/10/wicket-extreme-consistent-urls.html
>>>
>>
>> Does appear to make stateless-looking urls AFTER you CLICK/REDIRECT
>> (looking at the example page referred on the site). Not BEFORE you
>> CLICK...
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org