You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@struts.apache.org by "Garner, Shawn" <sh...@pearson.com> on 2006/01/12 20:50:35 UTC

[JSF/SHALE] 403 error

http://localhost:8101/totwcf/totwcf07/
<http://localhost:8101/totwcf/totwcf07/> 

 

I have a faces-totwcf.xml file that is bound in jrun to totwcf context.


When I visit  <http://localhost:8101/totwcf/totwcf07/>
http://localhost:8101/totwcf/totwcf07/ I get a 403 error (You are not
authorized to view this page)


I'm expecting it to take me to the summary page because I have this defined:

 

<navigation-rule>

    <from-view-id>*</from-view-id>

    <navigation-case>

      <from-outcome>home</from-outcome>

      <to-view-id>/summary.jsp</to-view-id>

    </navigation-case>

  </navigation-rule>

 

Shouldn't this go to this page?

 

 

 

Shawn


**************************************************************************** 
This email may contain confidential material. 
If you were not an intended recipient, 
Please notify the sender and delete all copies. 
We may monitor email to and from our network. 
****************************************************************************

Re: [JSF/SHALE] 403 error

Posted by Craig McClanahan <cr...@apache.org>.
On 1/12/06, Garner, Shawn <sh...@pearson.com> wrote:
>
> http://localhost:8101/totwcf/totwcf07/
> <http://localhost:8101/totwcf/totwcf07/>
>
>
>
> I have a faces-totwcf.xml file that is bound in jrun to totwcf context.
>
>
> When I visit  <http://localhost:8101/totwcf/totwcf07/>
> http://localhost:8101/totwcf/totwcf07/ I get a 403 error (You are not
> authorized to view this page)
>
>
> I'm expecting it to take me to the summary page because I have this
> defined:
>
>
>
> <navigation-rule>
>
>     <from-view-id>*</from-view-id>
>
>     <navigation-case>
>
>       <from-outcome>home</from-outcome>
>
>       <to-view-id>/summary.jsp</to-view-id>
>
>     </navigation-case>
>
>   </navigation-rule>


HTTP status codes other than 200 will always trump navigation rules :-).
One way to approach this would be to define an error page for the 403 error
that does the right thing.

Craig