Hi Stefan, did you already had the time to look at the 500 status code in case of canceled requests?
Stefan Am 25.01.2017 um 15:55 schrieb Stefan Priebe - Profihost AG: > > Am 25.01.2017 um 15:50 schrieb Stefan Eissing: >> >>> Am 25.01.2017 um 15:31 schrieb Stefan Priebe - Profihost AG >>> <s.pri...@profihost.ag>: >>> >>> Chrome docs says: >>> >>> "cancelled / net::ERR_ABORTED is intended to only be generated when a >>> user action causes a load to be interrupted. This can happen when a new >>> navigation interrupts an existing one, or when the user clicks the STOP >>> button" >>> >>> This matches my click assumption. I think it's just wrong that mod_http2 >>> generates a 500 in the logs. >> >> I agree. Might be a new one related to the 304 fix in 1.8.10. > > Would be great if you can have a look. It confuses the users while > reading their logs. > > I also saw some more entries with 0 byte size in logs if there is no > body. http/1.1 logs the header size as well. > > Greets, > Stefan > >>> >>> Stefan >>> >>> Am 25.01.2017 um 15:27 schrieb Stefan Priebe - Profihost AG: >>>> Am 25.01.2017 um 14:57 schrieb Yann Ylavic: >>>>> Hi, >>>>> >>>>> On Wed, Jan 25, 2017 at 2:46 PM, Stefan Priebe - Profihost AG >>>>> <s.pri...@profihost.ag> wrote: >>>>>> >>>>>> Is this a bug or a feature? Is it correct that it logs a 500 code? >>>>> >>>>> ErrorLog's file should tell more about the error. >>>> >>>> No error log does not have an entry with the same or nearly the same >>>> timestamp. >>>> >>>> Stefan >>>> >>>>> >>>>> Regards, >>>>> Yann. >>>>> >> >> Stefan Eissing >> >> <green/>bytes GmbH >> Hafenstrasse 16 >> 48155 Münster >> www.greenbytes.de >>
