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

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"

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"

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"

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 60719] Incremental IndexOptions in global server context are ignored

https://bz.apache.org/bugzilla/show_bug.cgi?id=60719 --- Comment #1 from Stefan Fritsch --- As a work-around, IndexOptions FancyIndexing IndexOptions SuppressDescription works. Though if the config is spread through many config files, it may be non-obvious that the lines

[Bug 60719] New: Incremental IndexOptions in global server context are ignored

https://bz.apache.org/bugzilla/show_bug.cgi?id=60719 Bug ID: 60719 Summary: Incremental IndexOptions in global server context are ignored Product: Apache httpd-2 Version: 2.4.25 Hardware: PC OS: Linux

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

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"

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"

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"

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 59829] Detect HTTPS marker from reverse proxy

https://bz.apache.org/bugzilla/show_bug.cgi?id=59829 --- Comment #20 from Yordan Gigov --- I have no way to test the ProxyProtocol addition, but I'm pretty sure I should have converted the server port using ntohs() when the protocol is version 2. That is lines 1056 and 1073

[Bug 58007] 400 Bad Request with fully qualified domain name over HTTPS

https://bz.apache.org/bugzilla/show_bug.cgi?id=58007 --- Comment #19 from Fred Morris --- (In reply to Yann Ylavic from comment #17) > Is it still reproducible with latest 2.4 (2.4.23)? Sorry, did not see this when the comment was posted. It's still reproducible today at

[Bug 59829] Detect HTTPS marker from reverse proxy

https://bz.apache.org/bugzilla/show_bug.cgi?id=59829 Yordan Gigov changed: What|Removed |Added Attachment #34711|0 |1 is

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

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"

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.

[Bug 60717] New: mod_proxy_http fails with 502 when backend sends 401 and closes connection immediately

https://bz.apache.org/bugzilla/show_bug.cgi?id=60717 Bug ID: 60717 Summary: mod_proxy_http fails with 502 when backend sends 401 and closes connection immediately Product: Apache httpd-2 Version: 2.4.25 Hardware: PC