Thanks for your input guys, after some experimenting I used the
annotation solution and got it working on 1.3 with some tweaking. I
had to take out the IResponseStrategy and just override respond(..)
in the RequestCycleProcessor instead. Also the redirection portion
had to be rewritten as included below to get the paths right.
I'll add my findings to the wiki page.
--- redirect portion that has to be changed to get the paths right ---
StringBuffer url = new StringBuffer("https://";);
url.append(httpServletRequest.getServerName());
url.append(":" + MyWebApplication.get().getHttpsPort());
url.append(webRequest.getHttpServletRequest().getContextPath());
url.append(webRequest.getServletPath());
webResponse.redirect(url.toString());
--- end of redirect portion ---
// Daniel
On 2007-09-25, at 08:00, Eelco Hillenius wrote:
All the other encode methods get the proper wicket URL but doesn't
prepend
the webapp URI which this final encode method does. Beyond filing
a RFE to
either make this method non-final or provide a postEncode
(RequestCycle,
IRequestTarget) method before URL encoding, we will have to copy
the entire
class and provide this behavior.
Thoughts?
I stand by my suggestion that you could just try to redirect to a
secure page. After that, the relative URLs stay secure no?
If I'm missing something, please tell.
Eelco
---------------------------------------------------------------------
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]
