My "redirect" method isn't overriding anything, it's just there to provide a shortcut to an external redirect, should I need it. Could it still be doing some damage, somehow?
I was using bookmarkable pages just before switching to Hybrids, at the same time I started using @RequireHttps, so they did work just fine. On Mon, Dec 21, 2009 at 4:51 PM, Jason Lea <ja...@kumachan.net.nz> wrote: > yay! > > But it is odd if setRedirect(true) didn't work when using a page instance. > I wonder if the there is an issue with HybridUrlCodingStrategy and > RequireHttps... can you mount the page you redirect to using a simple > bookmarkable page and see if it works? > > I also noticed you have a method on your BasePage class called > redirect(url) that disables wicket redirect... does that get called when you > use setRedirect(true)? > > > > VGJ wrote: > >> Jason...excellent! setResponsePage(UserAccount.class) did the trick! >> Thanks! Using setRedirect(true) didn't have any effect however. I had to >> redirect to the page class rather than a new instance of it. >> >> This works for me right now...but what happens when I'd like to pass >> parameters into the constructor of the page I'm redirecting to? >> >> -v >> >> > -- > Jason Lea > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
