Re: Change of status code for ClientAbortExceptions - bug?

> I also saw that with 8.5.20 the %X accessLog format was added, which I might > be able to use to differentiate between "real" 500 server-errors and client > disconnects. > > Best Regards > Andreas > > > > > -- > View this message in context:

Re: Change of status code for ClientAbortExceptions - bug?

Best Regards Andreas -- View this message in context: http://tomcat.10.x6.nabble.com/Change-of-status-code-for-ClientAbortExceptions-bug-tp5063738p5066604.html Sent from the Tomcat - User mailing list archive at Nabble.com. -

Re: Change of status code for ClientAbortExceptions - bug?

On 06/06/17 23:11, Konstantin Kolinko wrote: > 2017-06-07 0:10 GMT+03:00 Mark Thomas : >> On 06/06/17 15:08, Thomas Eliassen wrote: >>> >>> Is there some way to avoid having it logged as a 500 in the access log then? >> >> At the moment, no. And my preference is to avoid creating

Re: Change of status code for ClientAbortExceptions - bug?

2017-06-07 0:10 GMT+03:00 Mark Thomas : > On 06/06/17 15:08, Thomas Eliassen wrote: >> >> Is there some way to avoid having it logged as a 500 in the access log then? > > At the moment, no. And my preference is to avoid creating new > configuration options unless we have to. > >>

Re: Change of status code for ClientAbortExceptions - bug?

On 06/06/17 15:08, Thomas Eliassen wrote: > > Is there some way to avoid having it logged as a 500 in the access log then? At the moment, no. And my preference is to avoid creating new configuration options unless we have to. > ClientAbortExceptions are so frequent that it really pollutes the

Re: Change of status code for ClientAbortExceptions - bug?

Is there some way to avoid having it logged as a 500 in the access log then? ClientAbortExceptions are so frequent that it really pollutes the access logs, drowns out 500s actually caused by the server side application, and makes monitoring and debugging based on the access logging a lot

Re: Change of status code for ClientAbortExceptions - bug?

Another one I failed to send to the list first time around... On 29/05/17 08:26, Thomas Eliassen wrote: > Hi, > > Since https://bz.apache.org/bugzilla/show_bug.cgi?id=60718 (r1783148 in > tc8.5.x), ClientAbortExceptions are logged in the access log as status 500, > changed from the previous

Change of status code for ClientAbortExceptions - bug?

Hi, Since https://bz.apache.org/bugzilla/show_bug.cgi?id=60718 (r1783148 in  tc8.5.x), ClientAbortExceptions are logged in the access log as status 500, changed from the previous status 200. Is this actually the desired behaviour? It doesn't seem appropriate to log a 500 as this isn't