Re: Change of status code for ClientAbortExceptions - bug?

2017-06-06 Thread Thomas Eliassen
harder. I'll also note that e.g. Jetty logs a 200 on ClientAbortExceptions. -- 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), Clie

Change of status code for ClientAbortExceptions - bug?

2017-05-29 Thread Thomas Eliassen
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 necessari