You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2004/06/28 22:17:17 UTC

DO NOT REPLY [Bug 29851] New: - Handling of error reports

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=29851>.
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=29851

Handling of error reports

           Summary: Handling of error reports
           Product: Tomcat 5
           Version: 5.0.25
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Catalina
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: jens.mueller@dbv-winterthur.de


And there seems to be a bug with the handling of error reports.

For every status-code greater than 400, tomcat generates a html-message wich 
will be send to the client.

If you set a status-code in a sevlet, wich is not listed in 
org.apache.catalina.valves.LocalStrings.properties (999 for example), the html-
message looks like this:

HTTP Status 999 - Cannot find message associated with key '999'.

( org.apache.catalina.util.StringManager.getStringInternal() - in the catch-
block null could be a better return value )

In my configuration I use tomcat with apache and mod_jk 1.2.5.

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org