you can extend webrequestcodingstrategy to do that... -igor
On Mon, Feb 22, 2010 at 8:02 AM, Andrea Aime <[email protected]> wrote: > Hi, > I have developed an application with Wicket that has > its own built-in security and now a user needs to use > it in a way that security is managed by a proxy instead. > > The way they can impose security is by url, and in theory > I could get away by using only bookmarkable pages that > contain a certain package name. > > The issue is, when the page contents change (validation, > showing/hiding panels, ...) the url changes and becomes > something generic like: > > http://host/app/?wicket:interface=:3:1::: > > Is there any way to force it to encode the url so that > it looks at least like: > > http://host/app/secured?wicket:interface:3:1::: > > when the page is recognized as a secure one? (in my > case those pages extend a certain base class that provides > security control... when that is enabled, that is, otherwise > it does nothing). > > Cheers > Andrea > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
