Hi,
I had a stateless login form that did actually not expire
... until I added an image as submit button.
Sorry to raise this topic again, but AFAIK this has not been answered
yet:
ImageButton - always stateful ?
http://apache-wicket.1842946.n4.nabble.com/ImageButton-always-stateful
login form that did actually not expire
... until I added an image as submit button.
Sorry to raise this topic again, but AFAIK this has not been answered
yet:
ImageButton - always stateful ?
http://apache-wicket.1842946.n4.nabble.com/ImageButton-always-stateful-td1875620.html
I feel I am
()
{
return getImageResource() == null
localizedImageResource.isStateless();
}
but that must be true.
On Fri, Aug 20, 2010 at 13:19, b...@actrix.gen.nz wrote:
Hi,
I had a stateless login form that did actually not expire
... until I added an image as submit button.
Sorry
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
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:
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
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
--
View this message in context:
http://www.nabble.com/Stateless-login-form--tp24757066p24782234.html
Sent from the Wicket - User mailing
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@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
Hi!
My login page html looks like this:
form id=loginForm method=post
action=https://www.mydomain.com/?wicket:interface=:0:loginForm::IFormSubmitListener::;
Can set some switch to make it more stateless? I would like the form
submit target to be a stateless url. Why? I assume that currently if
You could either:
1 - override isStateless and return true
or
2 - make it submit to a bookmarkable page and process the input from
the PageParameters
--
Jeremy Thomerson
http://www.wickettraining.com
On Fri, Jul 31, 2009 at 9:07 AM, Martin
Makundimartin.maku...@koodaripalvelut.com wrote:
1 - override isStateless and return true
Will the form work ok? What about retry: if there are validation
errors, will such a stateless page work?
2 - make it submit to a bookmarkable page and process the input from
the PageParameters
q1: Will I have to manually hack the submit target?
q2:
If I understood correctly, you might find this interesting:
http://day-to-day-stuff.blogspot.com/2008/10/wicket-extreme-consistent-urls.html
Francisco
2009/7/31 Martin Makundi martin.maku...@koodaripalvelut.com:
1 - override isStateless and return true
Will the form work ok? What about retry:
Seems funny if wicket does not have robust login page capability
out-of-the-box ;)
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
13 matches
Mail list logo
