Actions
Bug #2751
closedmod_proxy closes connection
Status:
Duplicate
Priority:
Normal
Category:
mod_proxy
Target version:
-
ASK QUESTIONS IN Forums:
Description
Since upgrading to 1.4.41 from 1.4.39 my proxy setup does not work anymore. lighttpd seems to close the connection to the backend server right after sending the headers. The frontend receives a 500 HTTP code.
This is what I see in my backend server:
Sep 2 13:56:57 : DEBUG 2016-09-02 13:56:57.259 [WebSession.cpp : 89] network recv 127.0.0.1:8080 <- 127.0.0.1 Sep 2 13:56:57 : GET /audit.log HTTP/1.0. Sep 2 13:56:57 : Host: 192.168.2.54. Sep 2 13:56:57 : User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:48.0) Gecko/20100101 Firefox/48.0. Sep 2 13:56:57 : Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8. Sep 2 13:56:57 : Accept-Language: en-US,en;q=0.5. Sep 2 13:56:57 : Accept-Encoding: gzip, deflate, br. Sep 2 13:56:57 : Referer: https://192.168.2.54/log-files/. Sep 2 13:56:57 : Authorization: Basic YWRtaW46ZXNpZXJz. Sep 2 13:56:57 : Upgrade-Insecure-Requests: 1. Sep 2 13:56:57 : Cache-Control: max-age=0. Sep 2 13:56:57 : X-Forwarded-For: 192.168.2.10, 127.0.0.1. Sep 2 13:56:57 : X-Host: 192.168.2.54, 192.168.2.54. Sep 2 13:56:57 : X-Forwarded-Proto: https, http. Sep 2 13:56:57 : Connection: close. Sep 2 13:56:57 : . Sep 2 13:56:57 : DEBUG 2016-09-02 13:56:57.262 [WebSession.cpp : 779] network closed 127.0.0.1:8080 <- 127.0.0.1
Removing server.max-keep-alive-requests = 0 from the config changes the behaviour slightly resulting in the connection being closed somewhat later (but still to early).
Updated by stbuehler over 8 years ago
- Is duplicate of Bug #2743: 1.4.40/41 mod_proxy, mod_scgi may trigger POLLHUP on *BSD,Darwin added
Updated by stbuehler over 8 years ago
- Status changed from New to Duplicate
- Target version deleted (
1.4.x)
See #2743
Actions
Also available in: Atom