I'm having the same problem and I can reproduce this in a quickstart, I just
want to check before creating a jira:
- In my quickstart I'm calling setRedirect(true) within the form submit
button's onSubmit(), is this the correct place to force a redirect?
- SignInPage has the @RequireHttps annotat
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 d
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
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 con
Here are a couple of things to try...
@RequireHttps checks when the request comes into wicket and issues a
redirect if it is on the wrong protocol.
I wonder if it is because you are using setResponsePage(new
ContactInfo()); without a redirect, so the @RequireHttps annotation is
not checked b
I see, I guess I misunderstood you. I wasn't able to reproduce it in a
separate test application, however. It has to be encountering something in
this particular application that is causing a problem. I just can't figure
out what that might be, exactly.
I would submit the small test case I made
VGJ,
You might have discovered a limitation of the system or a bug. As I
wrote, I would recommend you make a testcase with all distracting
detail removed and submit it as a jira issue, then post a link to the
the issue here.
I understand your frustration, but I think the above would be the best
in
Well, I'm still unable to spot anything strange. No matter what page I
annotate, it doesn't switch to https until the form is submitted. It then
goes to https (as if it's redirecting to itself?) and triggers the
validation on the page, even if the correct fields are filled in. No matter
what pag
Hi VGJ,
If, as you say you can reproduce this in your storefront app no matter
where you use it then you may want to reduce this to a testcase and
create a jira issue from it.
You are already writing that you can reproduce it and consequently it
would be only a matter of removing all distracting
I was unable to re-create it in a simple web app w/ a few pages. However,
no matter where I use it in my storefront app, it happens.
It's very strange because it starts a page "late". I put the annotation on
the User Account page, yet it doesn't switch to https until I reach the
*following* page
I'll create one and post it, if I can.
-v
On Fri, Dec 18, 2009 at 9:21 AM, Igor Vaynberg wrote:
> can you recreate in a quickstart?
>
> -igor
>
> On Fri, Dec 18, 2009 at 7:56 AM, VGJ wrote:
> > I'm now using @RequireHttps to switch to https on certain pages but it's
> not
> > quite working righ
can you recreate in a quickstart?
-igor
On Fri, Dec 18, 2009 at 7:56 AM, VGJ wrote:
> I'm now using @RequireHttps to switch to https on certain pages but it's not
> quite working right.
>
> In our storefront app, I'm switching to https at the point in the checkout
> process where you view your c
I'm now using @RequireHttps to switch to https on certain pages but it's not
quite working right.
In our storefront app, I'm switching to https at the point in the checkout
process where you view your cart, and then proceed to a page to either login
or create an account. When I submit my username
13 matches
Mail list logo
