You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Stefan Priebe - Profihost AG <s....@profihost.ag> on 2017/01/25 13:46:30 UTC
mod_http2 and canceled requests logs status 500 internal server error
code
Hello,
while digging through some apache logfiles i saw some strange entries:
"GET URL HTTP/2.0" 500 0
They all had a 500 status error code and a size of 0.
I'm able to reproduce them while clicking fast on a php site. For each
log line with status code 500 i get a STATUS (canceled) in my chrome
developer console. It seems it happens if i click a new link before the
first click got a response back from the server.
Is this a bug or a feature? Is it correct that it logs a 500 code?
Greets,
Stefan
Re: mod_http2 and canceled requests logs status 500 internal server
error code
Posted by Stefan Priebe - Profihost AG <s....@profihost.ag>.
Hi,
Am 27.01.2017 um 18:59 schrieb Stefan Eissing:
> Out now: https://github.com/icing/mod_h2/releases/tag/1.8.11 fresh from Apache svn trunk+2.4.x
>
> I could not reproduce the 500 behaviour, but added a check on the recent change on response generation. Hope this helps.
thanks will report back most probably on monday.
Stefan
> Cheers, Stefan
>
>> Am 26.01.2017 um 16:36 schrieb Stefan Eissing <st...@greenbytes.de>:
>>
>> Hi, will do that tomorrow.
>>
>>> Am 26.01.2017 um 16:35 schrieb Stefan Priebe - Profihost AG <s....@profihost.ag>:
>>>
>>> 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....@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....@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
>>>>>
>>
>> Stefan Eissing
>>
>> <green/>bytes GmbH
>> Hafenstrasse 16
>> 48155 M�nster
>> www.greenbytes.de
>>
>
> Stefan Eissing
>
> <green/>bytes GmbH
> Hafenstrasse 16
> 48155 M�nster
> www.greenbytes.de
>
Re: mod_http2 and canceled requests logs status 500 internal server
error code
Posted by Stefan Eissing <st...@greenbytes.de>.
Out now: https://github.com/icing/mod_h2/releases/tag/1.8.11 fresh from Apache svn trunk+2.4.x
I could not reproduce the 500 behaviour, but added a check on the recent change on response generation. Hope this helps.
Cheers, Stefan
> Am 26.01.2017 um 16:36 schrieb Stefan Eissing <st...@greenbytes.de>:
>
> Hi, will do that tomorrow.
>
>> Am 26.01.2017 um 16:35 schrieb Stefan Priebe - Profihost AG <s....@profihost.ag>:
>>
>> 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....@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....@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
>>>>
>
> Stefan Eissing
>
> <green/>bytes GmbH
> Hafenstrasse 16
> 48155 Münster
> www.greenbytes.de
>
Stefan Eissing
<green/>bytes GmbH
Hafenstrasse 16
48155 Münster
www.greenbytes.de
Re: mod_http2 and canceled requests logs status 500 internal server
error code
Posted by Stefan Eissing <st...@greenbytes.de>.
Hi, will do that tomorrow.
> Am 26.01.2017 um 16:35 schrieb Stefan Priebe - Profihost AG <s....@profihost.ag>:
>
> 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....@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....@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
>>>
Stefan Eissing
<green/>bytes GmbH
Hafenstrasse 16
48155 Münster
www.greenbytes.de
Re: mod_http2 and canceled requests logs status 500 internal server
error code
Posted by Stefan Priebe - Profihost AG <s....@profihost.ag>.
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....@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....@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
>>
Re: mod_http2 and canceled requests logs status 500 internal server
error code
Posted by Stefan Priebe - Profihost AG <s....@profihost.ag>.
Hi,
Am 25.01.2017 um 15:59 schrieb Eric Covener:
> On Wed, Jan 25, 2017 at 9:55 AM, Stefan Priebe - Profihost AG
> <s....@profihost.ag> wrote:
>> 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.
>
> What's your logformat? Apache doesn't count headers in %b. If it's
> zero bytes, a - is logged. I suggest adding %X while looking at this
> issue to.
i'm using and we're calculating some value from them. Need to recheck.
Main problem can't reproduce this with my "slow" wlan notebook connection.
%O %{instream}n %I
Stefan
Re: mod_http2 and canceled requests logs status 500 internal server
error code
Posted by Eric Covener <co...@gmail.com>.
On Wed, Jan 25, 2017 at 9:55 AM, Stefan Priebe - Profihost AG
<s....@profihost.ag> wrote:
> 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.
What's your logformat? Apache doesn't count headers in %b. If it's
zero bytes, a - is logged. I suggest adding %X while looking at this
issue to.
--
Eric Covener
covener@gmail.com
Re: mod_http2 and canceled requests logs status 500 internal server
error code
Posted by Stefan Priebe - Profihost AG <s....@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....@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....@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
>
Re: mod_http2 and canceled requests logs status 500 internal server
error code
Posted by Stefan Eissing <st...@greenbytes.de>.
> Am 25.01.2017 um 15:31 schrieb Stefan Priebe - Profihost AG <s....@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.
>
> 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....@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
Re: mod_http2 and canceled requests logs status 500 internal server
error code
Posted by Stefan Priebe - Profihost AG <s....@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.
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....@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.
>>
Re: mod_http2 and canceled requests logs status 500 internal server
error code
Posted by Stefan Priebe - Profihost AG <s....@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....@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.
>
Re: mod_http2 and canceled requests logs status 500 internal server
error code
Posted by Yann Ylavic <yl...@gmail.com>.
Hi,
On Wed, Jan 25, 2017 at 2:46 PM, Stefan Priebe - Profihost AG
<s....@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.
Regards,
Yann.