DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUGĀ·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=42315>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED ANDĀ·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=42315


[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |




------- Additional Comments From [EMAIL PROTECTED]  2007-05-14 16:55 -------
Mark,

I had already checked SRV.11 specs before posting this bug. Sorry, but it 
makes no sense that when you point your browser to 
http://www.example.com/errors/500.htm Tomcat serves the page prefectly, but 
when an Exception occurs on the default servlet it can't access to that same 
location and the log shows the following:

SEVERE: Exception Processing ErrorPage[errorCode=500, location=/errors/500.htm

The SRV.11 specs need to be ALWAYS fulfilled in the same way. If I can access 
to a static ressource by pointing my browser to a certain page, that same page 
should also be served when stated as an error-page of that webapp.

Please, could you re-check the config details I provided? I may be wrong, but 
I continue to think that it's a bug.

Thanks!

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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

Reply via email to