I've attached a quickstart that exhibits this behavior.

Run Start, and access locally at: localhost:8080/gateway

Then try hitting: localhost:8080/target

While both approaches intercept the destination page (TargetPage), the
first case displays the Ajax Response content after auth.  The second case
works as expected.

Enter anything for user and password.



On Mon, May 6, 2013 at 11:04 AM, Nick Pratt <nbpr...@gmail.com> wrote:

> Im trying to redirect a user from an emailed link to an authenticated
> page.  The user clicks the link, I show a page (after checking the link
> validity etc.), and then using an AjaxTimerBehavior, I instantiate an
> auth-protected page, and invoke setResponsePage( myPage );
>
> Wicket then shows the login form, and after successful authentication, the
> browser then shows the XML content of any empty <ajax-response/> instead of
> the target page.  I see
> the org.apache.wicket.request.RequestHandlerStack$ReplaceHandlerException
> being thrown when I invoke continueToOriginalDestination();
>
> Ive also tried invoking requestCycle.scheduleRequestHandlerAfterCurrent()
> and requestCycle.replaceAllRequestHandlers() instead of setResponsePage()
> but I hit the same problem.
>
> Im using Wicket 6.7.0.
>
> Should I be able to redirect the user to an auth protected page on an Ajax
> timer callback like this?
>
> Nick
>

Attachment: quickstart.tar.gz
Description: GNU Zip compressed data

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Reply via email to