Re: Transfer From HTTPS To Non-HTTPS JSF Page

[Peter Cheung]

After I changed the navigation rule of the link to use <redirect/>, the URL on the browser did show the correct one, and then the warning ("about to leave non-secure page") dialog box popped up, but after I clicked "ok", the parameters that were passed together were failed to pass to the subsequent page. I also tried to redirect to a intermediate JSF page, and that page in turn put the parameter to the parameterMap in the request scope, but still the following page didn't get the parameters. I wonder if there is any way to get around this problem. Tks. 

On 1/25/06, Matthias Wessendorf <[EMAIL PROTECTED]> wrote:

On 1/25/06, Peter Cheung <[EMAIL PROTECTED]> wrote:
> I am working on a app. has a mix of HTTPS and non-HTTPS pages. Since the
> browser doesn't show the URL of the current JSF page(showing 1 URL behind),
> when the user first gets from a HTTPS to a non-HTTPS JSF page, there is no
> warning (produced by the IE) about leaving HTTPS, but once they move to one
> more non-HTTPS page, the warning of about to leave HTTPS page appears. That
> is very misleading to the user. I wonder if there is any way to force the
> display of the URL of the current JSF page.

using <redirect/> inside of your navigation rulez (faces-config.xml).

but this calls externalContext.redirect() (which itself calls
Facescontext.responseComplete())

-Matthias