Re: 403 error page not being displayed

[Jason Lea]

I couldn't see any.  But could you modify the GZIPResponseWrapper so 
that the sendError() or setStatus() methods can keep a copy of the 
status and add a getStatus() method so you can retrieve it later?

Matt Raible wrote:

OK, well that Filter isn't any better - anyone know how to get the
HTTP_STATUS code so I can disable the filter when the error-code is 403?
Thanks,

Matt

 

-Original Message-
From: Matt Raible [mailto:[EMAIL PROTECTED] 
Sent: Thursday, January 08, 2004 1:14 PM
To: 'Struts Users Mailing List'
Subject: RE: 403 error page not being displayed

I'm currently experiencing the issue with Tomcat 4.1.29, JDK 
1.4.2 on Windows XP and Fedora Core 1.  The header (from 
Mozilla) looks fine:

HTTP/1.x 403 User is not authorized to access action /editUser
Content-Type: text/html;charset=ISO-8859-1
Content-Language: en-US
Transfer-Encoding: chunked
Date: Thu, 08 Jan 2004 19:51:50 GMT
Server: Apache-Coyote/1.1
After further review it looks like my Gzip CompressionFilter
(http://tinyurl.com/25xva) is hosing things up - bout time I 
get a new one (http://tinyurl.com/3aaoy).

Thanks,

Matt

   

-Original Message-
From: Kris Schneider [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 08, 2004 12:05 PM
To: Struts Users Mailing List
Subject: Re: 403 error page not being displayed
Huh. Both 4.1.29 and 5.0.16 seem to work for 400 and 403 with
a simple error-page test (no Struts involved). AFAIK, the 
roles check is performed within RequestProcessor.processRoles 
which just does an HttpServletResponse.sendError if the user 
in not in the required role. At that point, the container 
should take over, so I'm not sure why it's not working for 
you. Big help, eh? ;-)

Quoting Kris Schneider <[EMAIL PROTECTED]>:

 

Looks like Struts 1.1 sends a 400 and the current nightly
   

sends a 403.
 

Maybe it's a TC bug. Which version are you using?

Quoting Matt Raible <[EMAIL PROTECTED]>:

   

I have roles configured on my "/editUser" action mapping so that
only administrator can access it.  When I try to request 
 

the page as
 

a "user", I get the default 403 page from Tomcat, rather than my
app's configured one.  In web.xml, I have a number of 
 

error pages 
   

defined, and 404 works OK:

   
   500
   /error.jsp
   
   
   400
   /index.jsp
   
   
   403
   /403.jsp
   
   
   404
   /404.jsp
   
In another application, that uses a very similar
 

structure, when a
 

403 is returned the user sees nothing - they're just
 

routed back to
 

the welcome file of the app.

The first app uses a Struts Nightly build from early
 

December, the
 

2nd uses Struts 1.1.  Any ideas why my 403.jsp error page isn't
displaying? I can pull it up fine if I type in the URL.
Thanks,

Matt
 

--
Kris Schneider <mailto:[EMAIL PROTECTED]>
D.O.Tech   <http://www.dotech.com/>
   

--
Kris Schneider <mailto:[EMAIL PROTECTED]>
D.O.Tech   <http://www.dotech.com/>
 

-
   

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
   



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
 



--
Jason Lea


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: 403 error page not being displayed

[Matt Raible]

OK, well that Filter isn't any better - anyone know how to get the
HTTP_STATUS code so I can disable the filter when the error-code is 403?

Thanks,

Matt

> -Original Message-
> From: Matt Raible [mailto:[EMAIL PROTECTED] 
> Sent: Thursday, January 08, 2004 1:14 PM
> To: 'Struts Users Mailing List'
> Subject: RE: 403 error page not being displayed
> 
> 
> I'm currently experiencing the issue with Tomcat 4.1.29, JDK 
> 1.4.2 on Windows XP and Fedora Core 1.  The header (from 
> Mozilla) looks fine:
> 
> HTTP/1.x 403 User is not authorized to access action /editUser
> Content-Type: text/html;charset=ISO-8859-1
> Content-Language: en-US
> Transfer-Encoding: chunked
> Date: Thu, 08 Jan 2004 19:51:50 GMT
> Server: Apache-Coyote/1.1
> 
> After further review it looks like my Gzip CompressionFilter
> (http://tinyurl.com/25xva) is hosing things up - bout time I 
> get a new one (http://tinyurl.com/3aaoy).
> 
> Thanks,
> 
> Matt
> 
> 
> > -Original Message-
> > From: Kris Schneider [mailto:[EMAIL PROTECTED]
> > Sent: Thursday, January 08, 2004 12:05 PM
> > To: Struts Users Mailing List
> > Subject: Re: 403 error page not being displayed
> > 
> > 
> > Huh. Both 4.1.29 and 5.0.16 seem to work for 400 and 403 with
> > a simple error-page test (no Struts involved). AFAIK, the 
> > roles check is performed within RequestProcessor.processRoles 
> > which just does an HttpServletResponse.sendError if the user 
> > in not in the required role. At that point, the container 
> > should take over, so I'm not sure why it's not working for 
> > you. Big help, eh? ;-)
> > 
> > Quoting Kris Schneider <[EMAIL PROTECTED]>:
> > 
> > > Looks like Struts 1.1 sends a 400 and the current nightly
> > sends a 403.
> > > Maybe it's a TC bug. Which version are you using?
> > > 
> > > Quoting Matt Raible <[EMAIL PROTECTED]>:
> > > 
> > > > I have roles configured on my "/editUser" action mapping so that
> > > > only administrator can access it.  When I try to request 
> > the page as
> > > > a "user", I get the default 403 page from Tomcat, rather than my
> > > > app's configured one.  In web.xml, I have a number of 
> error pages 
> > > > defined, and 404 works OK:
> > > > 
> > > > 
> > > > 500
> > > > /error.jsp
> > > > 
> > > > 
> > > > 400
> > > > /index.jsp
> > > > 
> > > > 
> > > > 403
> > > > /403.jsp
> > > > 
> > > > 
> > > > 404
> > > > /404.jsp
> > > > 
> > > > 
> > > > In another application, that uses a very similar
> > structure, when a
> > > > 403 is returned the user sees nothing - they're just
> > routed back to
> > > > the welcome file of the app.
> > > > 
> > > > The first app uses a Struts Nightly build from early
> > December, the
> > > > 2nd uses Struts 1.1.  Any ideas why my 403.jsp error page isn't
> > > > displaying? I can pull it up fine if I type in the URL.
> > > > 
> > > > Thanks,
> > > > 
> > > > Matt
> > > 
> > > --
> > > Kris Schneider <mailto:[EMAIL PROTECTED]>
> > > D.O.Tech   <http://www.dotech.com/>
> > 
> > --
> > Kris Schneider <mailto:[EMAIL PROTECTED]>
> > D.O.Tech   <http://www.dotech.com/>
> > 
> > 
> -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> > 
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: 403 error page not being displayed

[Matt Raible]

I'm currently experiencing the issue with Tomcat 4.1.29, JDK 1.4.2 on
Windows XP and Fedora Core 1.  The header (from Mozilla) looks fine:

HTTP/1.x 403 User is not authorized to access action /editUser
Content-Type: text/html;charset=ISO-8859-1
Content-Language: en-US
Transfer-Encoding: chunked
Date: Thu, 08 Jan 2004 19:51:50 GMT
Server: Apache-Coyote/1.1

After further review it looks like my Gzip CompressionFilter
(http://tinyurl.com/25xva) is hosing things up - bout time I get a new
one (http://tinyurl.com/3aaoy).

Thanks,

Matt


> -Original Message-
> From: Kris Schneider [mailto:[EMAIL PROTECTED] 
> Sent: Thursday, January 08, 2004 12:05 PM
> To: Struts Users Mailing List
> Subject: Re: 403 error page not being displayed
> 
> 
> Huh. Both 4.1.29 and 5.0.16 seem to work for 400 and 403 with 
> a simple error-page test (no Struts involved). AFAIK, the 
> roles check is performed within RequestProcessor.processRoles 
> which just does an HttpServletResponse.sendError if the user 
> in not in the required role. At that point, the container 
> should take over, so I'm not sure why it's not working for 
> you. Big help, eh? ;-)
> 
> Quoting Kris Schneider <[EMAIL PROTECTED]>:
> 
> > Looks like Struts 1.1 sends a 400 and the current nightly 
> sends a 403. 
> > Maybe it's a TC bug. Which version are you using?
> > 
> > Quoting Matt Raible <[EMAIL PROTECTED]>:
> > 
> > > I have roles configured on my "/editUser" action mapping so that 
> > > only administrator can access it.  When I try to request 
> the page as 
> > > a "user", I get the default 403 page from Tomcat, rather than my 
> > > app's configured one.  In web.xml, I have a number of error pages 
> > > defined, and 404 works OK:
> > > 
> > > 
> > > 500
> > > /error.jsp
> > > 
> > > 
> > > 400
> > > /index.jsp
> > > 
> > > 
> > > 403
> > > /403.jsp
> > > 
> > > 
> > > 404
> > > /404.jsp
> > > 
> > > 
> > > In another application, that uses a very similar 
> structure, when a 
> > > 403 is returned the user sees nothing - they're just 
> routed back to 
> > > the welcome file of the app.
> > > 
> > > The first app uses a Struts Nightly build from early 
> December, the 
> > > 2nd uses Struts 1.1.  Any ideas why my 403.jsp error page isn't 
> > > displaying? I can pull it up fine if I type in the URL.
> > > 
> > > Thanks,
> > > 
> > > Matt
> > 
> > --
> > Kris Schneider <mailto:[EMAIL PROTECTED]>
> > D.O.Tech   <http://www.dotech.com/>
> 
> -- 
> Kris Schneider <mailto:[EMAIL PROTECTED]>
> D.O.Tech   <http://www.dotech.com/>
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: 403 error page not being displayed

[Kris Schneider]

Huh. Both 4.1.29 and 5.0.16 seem to work for 400 and 403 with a simple
error-page test (no Struts involved). AFAIK, the roles check is performed within
RequestProcessor.processRoles which just does an HttpServletResponse.sendError
if the user in not in the required role. At that point, the container should
take over, so I'm not sure why it's not working for you. Big help, eh? ;-)

Quoting Kris Schneider <[EMAIL PROTECTED]>:

> Looks like Struts 1.1 sends a 400 and the current nightly sends a 403.
> Maybe
> it's a TC bug. Which version are you using?
> 
> Quoting Matt Raible <[EMAIL PROTECTED]>:
> 
> > I have roles configured on my "/editUser" action mapping so that only
> > administrator can access it.  When I try to request the page as a
> > "user", I get the default 403 page from Tomcat, rather than my app's
> > configured one.  In web.xml, I have a number of error pages defined, and
> > 404 works OK:
> > 
> > 
> > 500
> > /error.jsp
> > 
> > 
> > 400
> > /index.jsp
> > 
> > 
> > 403
> > /403.jsp
> > 
> > 
> > 404
> > /404.jsp
> > 
> > 
> > In another application, that uses a very similar structure, when a 403
> > is returned the user sees nothing - they're just routed back to the
> > welcome file of the app.  
> > 
> > The first app uses a Struts Nightly build from early December, the 2nd
> > uses Struts 1.1.  Any ideas why my 403.jsp error page isn't displaying?
> > I can pull it up fine if I type in the URL.
> > 
> > Thanks,
> > 
> > Matt
> 
> -- 
> Kris Schneider 
> D.O.Tech   

-- 
Kris Schneider 
D.O.Tech   

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: 403 error page not being displayed

[Kris Schneider]

Looks like Struts 1.1 sends a 400 and the current nightly sends a 403. Maybe
it's a TC bug. Which version are you using?

Quoting Matt Raible <[EMAIL PROTECTED]>:

> I have roles configured on my "/editUser" action mapping so that only
> administrator can access it.  When I try to request the page as a
> "user", I get the default 403 page from Tomcat, rather than my app's
> configured one.  In web.xml, I have a number of error pages defined, and
> 404 works OK:
> 
> 
> 500
> /error.jsp
> 
> 
> 400
> /index.jsp
> 
> 
> 403
> /403.jsp
> 
> 
> 404
> /404.jsp
> 
> 
> In another application, that uses a very similar structure, when a 403
> is returned the user sees nothing - they're just routed back to the
> welcome file of the app.  
> 
> The first app uses a Struts Nightly build from early December, the 2nd
> uses Struts 1.1.  Any ideas why my 403.jsp error page isn't displaying?
> I can pull it up fine if I type in the URL.
> 
> Thanks,
> 
> Matt

-- 
Kris Schneider 
D.O.Tech   

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]