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 2008/09/12 22:17:26 UTC

DO NOT REPLY [Bug 45796] New: 505 Errors are not logged in the access log

https://issues.apache.org/bugzilla/show_bug.cgi?id=45796

           Summary: 505 Errors are not logged in the access log
           Product: Tomcat 5
           Version: 5.5.23
          Platform: PC
        OS/Version: Windows Server 2003
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Connector:Coyote
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: eric.bloch@gmail.com


Easy to verify via

% telnet host 8080
GET / foo bar HTTP/1.1
Host: host

Then
curl http://host:8080/

then look in access log.

I realize its debatable whether or not 505s should be logged, but I am trying
to debug a 505 right now and it should would be helpful.  At the very least, a
config option that enabled logging of 505s would be nice.  Fwiw, Apache HTTPd
2.0 logs 505s.


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

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

DO NOT REPLY [Bug 45796] 505 Errors are not logged in the access log

Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=45796





--- Comment #2 from Eric Bloch <er...@gmail.com>  2008-09-15 13:57:35 PST ---
Btw, logging 505s also seems useful wrt tracking down potential abuse.  As I
persoused the src code it seems like there are other error responses that may
not get logged as well, including some 400s, 500s, and 503s.




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

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

DO NOT REPLY [Bug 45796] 505 Errors are not logged in the access log

Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=45796


Mark Thomas <ma...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX




--- Comment #1 from Mark Thomas <ma...@apache.org>  2008-09-15 12:22:06 PST ---
Tomcat rejects the request as early as possible in the processing chain. This
particular error causes the request to be rejected a fair way before the
request reaches the access log valve.

It would require fairly large changes to the request processing chain for this
request (or all requests) to reach the access log valve.

I am therefore marking this as WONTFIX. To debug this issue you could use httpd
in front of Tomcat with mod_proxy_http and utilise httpd's access logging if it
gives you what you need.


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

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