Hi Nick,
Did you find a solution for moving from HTTP to
HTTPS and then back.
I need to do the same in one of the wicket projects
i am working.
At the moment i am using acegi's ChannelProcessingFilter to do this.
Don't know if this is the ideal solution, if there
is any better (Wicket)
I'm working on adding the functionality to Wicket. Should be a few more days. On 12/20/05, Dipu [EMAIL PROTECTED]
wrote:
Hi Nick,
Did you find a solution for moving from HTTP to
HTTPS and then back.
I need to do the same in one of the wicket projects
i am working.
At the moment i am
I don't know. What is the main problem you are having (hard coding
url's probably), and do you have an idea of how support should look
like? For instance, would it (ssl/ normal) be something you could
configure your page maps with?
Any other people been doing this? How do competing frameworks
I'd like to either see something like WebPage.isSecure() or WebPage.getScheme(), like Christian suggested. I don't think redirecting to an HTTPS page would work in checkAccess() because I believe form properties from a POST would be lost.
On 12/6/05, Christian Essl [EMAIL PROTECTED] wrote:
There
I'm a bit tied up at the moment, but patches would be welcome :)
Eelco
On 12/6/05, Nick Heudecker [EMAIL PROTECTED] wrote:
I'd like to either see something like WebPage.isSecure() or
WebPage.getScheme(), like Christian suggested. I don't think redirecting to
an HTTPS page would work in
On 12/6/05, Nick Heudecker [EMAIL PROTECTED] wrote:
I don't think redirecting to
an HTTPS page would work in checkAccess() because I believe form properties
from a POST would be lost.
Unless you redirect with 307 which is supported by modern browsers
(umm, differently). But in this case the
Okay. I'm guessing this would impact WebPage and possibly the Link class. Anything else you think I should look at?On 12/6/05, Eelco Hillenius
[EMAIL PROTECTED] wrote:I'm a bit tied up at the moment, but patches would be welcome :)
EelcoOn 12/6/05, Nick Heudecker [EMAIL PROTECTED] wrote: I'd like
I'd take a look at Page.urlFor()-urlPrefix().
However I do not know how this plays together with the new refactorings.
Christian
On Tue, 6 Dec 2005 15:37:24 -0600, Nick Heudecker [EMAIL PROTECTED]
wrote:
Okay. I'm guessing this would impact WebPage and possibly the Link
class.
Anything
