Hi,

I has the following use case: I have some public pages (should be served
over HTTP)  containing a sign in "panel" which must be submitted over HTTPs.
I have though of doing this as follows:

-use an iframe to host the sign in "panel": actually it would be a page
served over HTTPs to the iframe.
-once the user signs in serve a page to the iframe that contains JavaScript
to get parent page to be redirected to the private area (served over HTTPs).

I do not tried the above but I assume it might work. My question is if there
is a cleaner/cleverer way to do this in wicket?

Thanks in advance,

Melinda

Reply via email to