0 Replies Latest reply on Jun 6, 2012 1:35 PM by Brian Johnson

    Seam 2.2.0 scheme redirection does not propagate request parameters

    Brian Johnson Newbie

      Using Seam 2.2.0

       

      Have the following wildcard scheme def in my pages.xml:

       

      <page view-id="*" scheme="http" />

       

      For some specific pages (password change, etc), the scheme is specified as https.  For all other view-id defs, no scheme is specified so the default of http is used.

       

      My problem is this, for a page that doesn't specify a scheme (and, hence, uses the default http), if the user attempts to visit the page using https, when Seam redirects to http, it drops the request parameters.  Near as I can tell, this is what happens:

       

      in org.jboss.seam.navigation.Pages.preRender(FacesContext) after we've determined there's a scheme mismatch, the following is called:

      Manager.instance().redirect(viewId);

       

      that lands me in org.jboss.seam.faces.FacesManager.redirect(String), where we call:

      redirect(viewId, null, true, true);

       

      See that null there?  That argument is the request parameter map.  Are we intentionally not propagating the request parameters in this case?  If so, can someone please enligten me as to why?

       

      Thanks in advance.