Priority: P3: Somewhat important
Affects Version/s: 5.12.10
Fix Version/s: None
Component/s: Network: HTTP
Environment:Ubuntu 20.04 and embedded Linux (buildroot compiled)
lighthhtpd server as frontend
When a request comes through a forward-proxy (lighttpd mod_proxy), the request is handled and the correct route is called but the response never comes back to the client until the Server is closed or disconnectFromHost is called on the socket
With a proxy redirecting all call behind a /API url on port 80 or 443 to the QhttpServer (on port 9000),
With a very simple server running on host 172.16.16.120 port 9000
And the lighttpd proxy running on 172.16.16.115
Modifying the sendResponse function to close the socket if it's a forward request make it works but it's not a good solution for websocket and the likes, the Forwarded header is not really a standard (lighttpd still use X-Forwarded-Host in my version (1.4.54)) and it doesn't solve the root cause of the problem
The parsed url is rather strange when the request has been forwarded (see forwarded_parsed_url.txt) but I don't think that it has any impact on the socket side.
I haven't found any cleaner way to get the responses so far.
Don't hesitate if I can provide anything else useful,