You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by kan <ka...@gmail.com> on 2008/11/26 17:27:43 UTC
continueToOriginalDestination and POST
I have a site which requires authentication. I've made it via
@AuthorizeInstantiation.
Works well. But if a bookmarkable page has a <form> with method POST,
and user presses "submit" after timeout, it redirects him to SignIn
screen. After successful login the site redirects back (usinig
continueToOriginalDestination) to the page and happens not very good
thing - method on form onSubmit is called but with no data on it,
because POST is lost during that redirects. Is there any easy reliable
solution of the problem?
--
WBR, kan.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: continueToOriginalDestination and POST
Posted by Jonas <ba...@gmail.com>.
I found a JIRA issue was filed for this a while back:
https://issues.apache.org/jira/browse/WICKET-1703
...but it hasn't been addressed yet...
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: continueToOriginalDestination and POST
Posted by jWeekend <jw...@cabouge.com>.
Kan,
If you are thinking of getting around this with a "heartbeat", Eelco
http://chillenious.wordpress.com/2007/06/19/how-to-create-a-text-area-with-a-heart-beat-with-wicket/
wrote about this a while back.
Regards - Cemal
http://www.jWeekend.co.uk http://j|Weekend.co.uk
kan-4 wrote:
>
> Yes, I am talking about timeouts.
> Actually... Maybe I want from wicket more than it was designed for. In
> some cases state of web-application could be on client-side and
> doesn't need to be in server-side session, only exception is
> auth-data. And I don't like fact that user faces with "page expired"
> error message or losses post data.
> But maybe yes, easier would be just make a periodic poll to keep session.
>
> 2008/11/26 Jeremy Thomerson <je...@wickettraining.com>:
>> You could add a feature request (and a patch?).
>>
>> My point was don't let them start on the form until they are signed in if
>> being signed in is required for submitting the form. This just makes
>> sense.
>>
>> Or, if what you're saying is that they are timing out while working on
>> the
>> form, add an ajax update behavior that will keep them signed in / session
>> current.
>>
>> On Wed, Nov 26, 2008 at 12:36 PM, kan <ka...@gmail.com> wrote:
>>
>>> A user has started to work with the form, then was distracted for 20
>>> minutes, then he comes back and presses "submit".
>>> Is it difficult to store PageParameters too?
>>>
>>> 2008/11/26 Jeremy Thomerson <je...@wickettraining.com>:
>>> > They shouldn't be able to access the bookmarkable page with the form
>>> (or,
>>> > access the page, but have the form hidden until signed-in). For
>>> > continueToOriginalDestination, IIRC, Wicket just stores the URL, so
>>> you
>>> > can't go back to a POST.
>>> >
>>> > On Wed, Nov 26, 2008 at 10:27 AM, kan <ka...@gmail.com> wrote:
>>> >
>>> >> I have a site which requires authentication. I've made it via
>>> >> @AuthorizeInstantiation.
>>> >> Works well. But if a bookmarkable page has a <form> with method POST,
>>> >> and user presses "submit" after timeout, it redirects him to SignIn
>>> >> screen. After successful login the site redirects back (usinig
>>> >> continueToOriginalDestination) to the page and happens not very good
>>> >> thing - method on form onSubmit is called but with no data on it,
>>> >> because POST is lost during that redirects. Is there any easy
>>> reliable
>>> >> solution of the problem?
>>> >>
>>> >> --
>>> >> WBR, kan.
>>> >>
>>> >> ---------------------------------------------------------------------
>>> >> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> >> For additional commands, e-mail: users-help@wicket.apache.org
>>> >>
>>> >>
>>> >
>>> >
>>> > --
>>> > Jeremy Thomerson
>>> > http://www.wickettraining.com
>>> >
>>>
>>>
>>>
>>> --
>>> WBR, kan.
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>
>>
>> --
>> Jeremy Thomerson
>> http://www.wickettraining.com
>>
>
>
>
> --
> WBR, kan.
>
> ---------------------------------------------------------------------
> 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/continueToOriginalDestination-and-POST-tp20704326p20711992.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: continueToOriginalDestination and POST
Posted by kan <ka...@gmail.com>.
Yes, I am talking about timeouts.
Actually... Maybe I want from wicket more than it was designed for. In
some cases state of web-application could be on client-side and
doesn't need to be in server-side session, only exception is
auth-data. And I don't like fact that user faces with "page expired"
error message or losses post data.
But maybe yes, easier would be just make a periodic poll to keep session.
2008/11/26 Jeremy Thomerson <je...@wickettraining.com>:
> You could add a feature request (and a patch?).
>
> My point was don't let them start on the form until they are signed in if
> being signed in is required for submitting the form. This just makes sense.
>
> Or, if what you're saying is that they are timing out while working on the
> form, add an ajax update behavior that will keep them signed in / session
> current.
>
> On Wed, Nov 26, 2008 at 12:36 PM, kan <ka...@gmail.com> wrote:
>
>> A user has started to work with the form, then was distracted for 20
>> minutes, then he comes back and presses "submit".
>> Is it difficult to store PageParameters too?
>>
>> 2008/11/26 Jeremy Thomerson <je...@wickettraining.com>:
>> > They shouldn't be able to access the bookmarkable page with the form
>> (or,
>> > access the page, but have the form hidden until signed-in). For
>> > continueToOriginalDestination, IIRC, Wicket just stores the URL, so you
>> > can't go back to a POST.
>> >
>> > On Wed, Nov 26, 2008 at 10:27 AM, kan <ka...@gmail.com> wrote:
>> >
>> >> I have a site which requires authentication. I've made it via
>> >> @AuthorizeInstantiation.
>> >> Works well. But if a bookmarkable page has a <form> with method POST,
>> >> and user presses "submit" after timeout, it redirects him to SignIn
>> >> screen. After successful login the site redirects back (usinig
>> >> continueToOriginalDestination) to the page and happens not very good
>> >> thing - method on form onSubmit is called but with no data on it,
>> >> because POST is lost during that redirects. Is there any easy reliable
>> >> solution of the problem?
>> >>
>> >> --
>> >> WBR, kan.
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> >> For additional commands, e-mail: users-help@wicket.apache.org
>> >>
>> >>
>> >
>> >
>> > --
>> > Jeremy Thomerson
>> > http://www.wickettraining.com
>> >
>>
>>
>>
>> --
>> WBR, kan.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
>
> --
> Jeremy Thomerson
> http://www.wickettraining.com
>
--
WBR, kan.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: continueToOriginalDestination and POST
Posted by Jeremy Thomerson <je...@wickettraining.com>.
You could add a feature request (and a patch?).
My point was don't let them start on the form until they are signed in if
being signed in is required for submitting the form. This just makes sense.
Or, if what you're saying is that they are timing out while working on the
form, add an ajax update behavior that will keep them signed in / session
current.
On Wed, Nov 26, 2008 at 12:36 PM, kan <ka...@gmail.com> wrote:
> A user has started to work with the form, then was distracted for 20
> minutes, then he comes back and presses "submit".
> Is it difficult to store PageParameters too?
>
> 2008/11/26 Jeremy Thomerson <je...@wickettraining.com>:
> > They shouldn't be able to access the bookmarkable page with the form
> (or,
> > access the page, but have the form hidden until signed-in). For
> > continueToOriginalDestination, IIRC, Wicket just stores the URL, so you
> > can't go back to a POST.
> >
> > On Wed, Nov 26, 2008 at 10:27 AM, kan <ka...@gmail.com> wrote:
> >
> >> I have a site which requires authentication. I've made it via
> >> @AuthorizeInstantiation.
> >> Works well. But if a bookmarkable page has a <form> with method POST,
> >> and user presses "submit" after timeout, it redirects him to SignIn
> >> screen. After successful login the site redirects back (usinig
> >> continueToOriginalDestination) to the page and happens not very good
> >> thing - method on form onSubmit is called but with no data on it,
> >> because POST is lost during that redirects. Is there any easy reliable
> >> solution of the problem?
> >>
> >> --
> >> WBR, kan.
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> >> For additional commands, e-mail: users-help@wicket.apache.org
> >>
> >>
> >
> >
> > --
> > Jeremy Thomerson
> > http://www.wickettraining.com
> >
>
>
>
> --
> WBR, kan.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
--
Jeremy Thomerson
http://www.wickettraining.com
Re: continueToOriginalDestination and POST
Posted by kan <ka...@gmail.com>.
A user has started to work with the form, then was distracted for 20
minutes, then he comes back and presses "submit".
Is it difficult to store PageParameters too?
2008/11/26 Jeremy Thomerson <je...@wickettraining.com>:
> They shouldn't be able to access the bookmarkable page with the form (or,
> access the page, but have the form hidden until signed-in). For
> continueToOriginalDestination, IIRC, Wicket just stores the URL, so you
> can't go back to a POST.
>
> On Wed, Nov 26, 2008 at 10:27 AM, kan <ka...@gmail.com> wrote:
>
>> I have a site which requires authentication. I've made it via
>> @AuthorizeInstantiation.
>> Works well. But if a bookmarkable page has a <form> with method POST,
>> and user presses "submit" after timeout, it redirects him to SignIn
>> screen. After successful login the site redirects back (usinig
>> continueToOriginalDestination) to the page and happens not very good
>> thing - method on form onSubmit is called but with no data on it,
>> because POST is lost during that redirects. Is there any easy reliable
>> solution of the problem?
>>
>> --
>> WBR, kan.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
>
> --
> Jeremy Thomerson
> http://www.wickettraining.com
>
--
WBR, kan.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: continueToOriginalDestination and POST
Posted by Jeremy Thomerson <je...@wickettraining.com>.
They shouldn't be able to access the bookmarkable page with the form (or,
access the page, but have the form hidden until signed-in). For
continueToOriginalDestination, IIRC, Wicket just stores the URL, so you
can't go back to a POST.
On Wed, Nov 26, 2008 at 10:27 AM, kan <ka...@gmail.com> wrote:
> I have a site which requires authentication. I've made it via
> @AuthorizeInstantiation.
> Works well. But if a bookmarkable page has a <form> with method POST,
> and user presses "submit" after timeout, it redirects him to SignIn
> screen. After successful login the site redirects back (usinig
> continueToOriginalDestination) to the page and happens not very good
> thing - method on form onSubmit is called but with no data on it,
> because POST is lost during that redirects. Is there any easy reliable
> solution of the problem?
>
> --
> WBR, kan.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
--
Jeremy Thomerson
http://www.wickettraining.com