[Bug 60681] Increase severity of "request failed: error reading the headers"

2023-05-16 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=60681 --- Comment #21 from alishakihn --- You have to tap the screen so that the bird flaps its wings, trying to keep a steady rhythm in order to pass through the pipes scattered through its path. https://flappy-bird.io -- You are receiving this

[Bug 60681] Increase severity of "request failed: error reading the headers"

2022-06-27 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=60681 --- Comment #20 from Peyton Busey --- Increase severity of "request failed: error reading the headers" https://wikiguide.tips/gmail-sign-up -- You are receiving this mail because: You are the assignee for the bug.

[Bug 60681] Increase severity of "request failed: error reading the headers"

2020-01-25 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=60681 --- Comment #20 from sandy45 --- What are the advantages of using an online billing program? One of the steps that every company should take at some point in its development is to move from manual activities to computer programs. Far from

[Bug 60681] Increase severity of "request failed: error reading the headers"

2019-09-05 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=60681 --- Comment #19 from jameslite123 --- Gmail Sign up is a free email service developed by Google. Users can access Gmail on the web and using third-party programs that synchronize email content through POP or IMAP protocols. You can use the

[Bug 60681] Increase severity of "request failed: error reading the headers"

2019-09-02 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=60681 --- Comment #18 from testbounty13...@gmail.com --- Just Curious to know the update. https://googleaccountlogin.com/google-drive-login/ -- You are receiving this mail because: You are the assignee for the bug.

[Bug 60681] Increase severity of "request failed: error reading the headers"

2019-08-15 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=60681 --- Comment #17 from rapclimber --- Kindly share update or progress on this. https://zohomaillogin.com/aol-mail-login/ -- You are receiving this mail because: You are the assignee for the bug.

[Bug 60681] Increase severity of "request failed: error reading the headers"

2019-07-24 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=60681 david guptil changed: What|Removed |Added URL||https://www.technical-help-

[Bug 60681] Increase severity of "request failed: error reading the headers"

2018-10-26 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=60681 --- Comment #15 from Matt --- Any progress on this? gmail sign up https://www.just4dummies.com/gmail-sign-up -- You are receiving this mail because: You are the assignee for the bug.

[Bug 60681] Increase severity of "request failed: error reading the headers"

2018-01-16 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=60681 --- Comment #14 from Ben RUBSON --- Hi, Eric, Jacob, William, and others :) Any progress on this ? Thank you again ! Ben -- You are receiving this mail because: You are the assignee for the bug.

[Bug 60681] Increase severity of "request failed: error reading the headers"

2017-02-15 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=60681 --- Comment #12 from William A. Rowe Jr. --- "Fail2ban already has an "apache-overflows" jail, which reads the ErrorLog. It would then really be convenient (and logical) to add to this existing jail a new rule to catch

[Bug 60681] Increase severity of "request failed: error reading the headers"

2017-02-10 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=60681 --- Comment #11 from Ben RUBSON --- William, thank you very much for your deep technical analysis ! > We do need a patch which alters the severity (to APLOG_NOTICE, imo) I would also be glad to have [notice] level

[Bug 60681] Increase severity of "request failed: error reading the headers"

2017-02-09 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=60681 --- Comment #10 from William A. Rowe Jr. --- Sorry for confusion, I should have stated 'request line', not 'header line': HTTP Connect: no record HTTP Timeout before the request line is read: no record HTTP Timeout after

[Bug 60681] Increase severity of "request failed: error reading the headers"

2017-02-09 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=60681 --- Comment #9 from William A. Rowe Jr. --- Sorry for confusion, I should have stated 'request line', not 'header line': HTTP Timeout before a request line is read: no record HTTP Timeout after request line is read, before

[Bug 60681] Increase severity of "request failed: error reading the headers"

2017-02-09 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=60681 --- Comment #8 from William A. Rowe Jr. --- Actually, let me reframe that. Leaving a breadcrumb of a faulty request which does *not* hit the access.log file is sensible. We do need a patch which alters the severity (to

[Bug 60681] Increase severity of "request failed: error reading the headers"

2017-02-09 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=60681 --- Comment #7 from William A. Rowe Jr. --- Flipping this back is the wrong course of action. The purpose of the error log is to alert and advise the operator or content maintainers of the server of those conditions under

[Bug 60681] Increase severity of "request failed: error reading the headers"

2017-02-09 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=60681 --- Comment #6 from Jacob Champion --- (In reply to Eric Covener from comment #2) > I don't think we should just flip the severity back, need a way to opt-in or > if the default changes again, an easy way to suppress

[Bug 60681] Increase severity of "request failed: error reading the headers"

2017-02-09 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=60681 --- Comment #5 from Ben RUBSON --- OK, thank you for your confirmation :) >From my point of view, re-increasing at least this one would be justified, as it allows to detect slowloris attacks. Apache 2.2 was released in

[Bug 60681] Increase severity of "request failed: error reading the headers"

2017-02-09 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=60681 --- Comment #4 from Eric Covener --- (In reply to Ben RUBSON from comment #3) > Thank you for your feedback Eric. > > > I don't think we should just flip the severity back, > Do you mean that this error was already set to

[Bug 60681] Increase severity of "request failed: error reading the headers"

2017-02-09 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=60681 --- Comment #3 from Ben RUBSON --- Thank you for your feedback Eric. > I don't think we should just flip the severity back, Do you mean that this error was already set to an error level different than DEBUG in the past ?

[Bug 60681] Increase severity of "request failed: error reading the headers"

2017-02-09 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=60681 --- Comment #2 from Eric Covener --- I don't think we should just flip the severity back, need a way to opt-in or if the default changes again, an easy way to suppress messages by prefix/ID. -- You are receiving this mail

[Bug 60681] Increase severity of "request failed: error reading the headers"

2017-02-09 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=60681 --- Comment #1 from Ben RUBSON --- Patch submitted : https://github.com/apache/httpd/pull/25 Thank you ! -- You are receiving this mail because: You are the assignee for the bug.