Hi Alex,
Normally you can throw a special exception, the
RestartResponseAtInterceptPageException. Unfortunately I do not think
this will work when the intercept page is external to Wicket.
So the only thing you can do, is put the original URL in a parameter to
the perl page, and let the perl
-
From: Erik van Oosten [EMAIL PROTECTED]
To: users@wicket.apache.org
Sent: 1/4/08 2:23 AM
Subject: Re: external login pages
Hi Alex,
Normally you can throw a special exception, the
RestartResponseAtInterceptPageException. Unfortunately I do not think
this will work when the intercept page
Subject: Re: external login pages
Hi Alex,
Normally you can throw a special exception, the
RestartResponseAtInterceptPageException. Unfortunately I do not think
this will work when the intercept page is external to Wicket.
So the only thing you can do, is put the original URL in a parameter
-
From: Erik van Oosten [EMAIL PROTECTED]
To: users@wicket.apache.org
Sent: 1/4/08 2:23 AM
Subject: Re: external login pages
Hi Alex,
Normally you can throw a special exception, the
RestartResponseAtInterceptPageException. Unfortunately I do not think
this will work when the intercept page
I am building a new wicket app that has to use an existing login
page. The legacy login page is written in perl and sets a login
cookie before redirecting the user back to a specified URL.
I'm hoping to keep things simple and use role-based authorization for
pages. In my authenticated
