https://bz.apache.org/bugzilla/show_bug.cgi?id=59045
Bug ID: 59045
Summary: AH01382: Request body read timeout triggered in
reverse proxy setup
Product: Apache httpd-2
Version: 2.4.17
Hardware: PC
OS: Linux
Status: NEW
Severity: major
Priority: P2
Component: mod_reqtimeout
Assignee: [email protected]
Reporter: [email protected]
Created attachment 33581
--> https://bz.apache.org/bugzilla/attachment.cgi?id=33581&action=edit
Debug output
Hi,
I'm currently facing a strange issue with Apache 2.4.17 running in a reverse
proxy setup. The web server terminates SSL, and requests are forwarded via AJP
to a Tomcat server.
It seems that mod_reqtimeout triggers a AH01382 for requests running longer
(>20s default request timeout), even though the web server already responded
with status code 200. This is triggered with both Worker and Event MPMs.
Attached is the debug output from a sample session. The request starts in line
1054, line 1153 shows the timeout error, while in line 1130 the 200 response is
already sent back to the client.
Please note the time difference of 50s between forwarding the request to the
client (line 1120), and getting back the response from the server (line 1121).
The AH01382 is NOT triggered if I increase the request body timeout to e.g.
900s.
Seems like mod_reqtimeout is triggered too late in the chain, so that the
request processing time on the backend server is wrongly taken into account.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
