https://bz.apache.org/bugzilla/show_bug.cgi?id=66537
Bug ID: 66537
Summary: large request serving times logged since upgrade to
2.4.56
Product: Apache httpd-2
Version: 2.4.56
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Core
Assignee: bugs@httpd.apache.org
Reporter: hamish@risingsoftware.com
Target Milestone: ---
I am logging the time to serve a request using %D (or %{us}T) in a log format.
Since upgrading from 2.4.55 to 2.4.56, I see a lot of requests logged as taking
over 10 seconds (and up to 35 seconds) to process.
All my traffic is reverse proxied to other applications over HTTP, ie I am
using HTTPD for SSL termination and request routing.
For example, one server recorded 100 requests all day requiring >10s yesterday,
but has already recorded >4500 in 5 hours since installing 2.4.56.
I don't see any difference when looking at the timing in the browser network
pane. The affected traffic seems to be a mix of HTTP/1.1 and 2.0.
I have keepalives on with a KeepAliveTimeout of 35. I wonder if it is counting
time until the connection is closed now?
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org
Bug ID: 66537
Summary: large request serving times logged since upgrade to
2.4.56
Product: Apache httpd-2
Version: 2.4.56
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Core
Assignee: bugs@httpd.apache.org
Reporter: hamish@risingsoftware.com
Target Milestone: ---
I am logging the time to serve a request using %D (or %{us}T) in a log format.
Since upgrading from 2.4.55 to 2.4.56, I see a lot of requests logged as taking
over 10 seconds (and up to 35 seconds) to process.
All my traffic is reverse proxied to other applications over HTTP, ie I am
using HTTPD for SSL termination and request routing.
For example, one server recorded 100 requests all day requiring >10s yesterday,
but has already recorded >4500 in 5 hours since installing 2.4.56.
I don't see any difference when looking at the timing in the browser network
pane. The affected traffic seems to be a mix of HTTP/1.1 and 2.0.
I have keepalives on with a KeepAliveTimeout of 35. I wonder if it is counting
time until the connection is closed now?
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org