Bug #3215
closedUnexpected buffering when backend using "X-LIGHTTPD-KBytes-per-second" header
Description
This issue is related to issue #3214
I'm running 2 lighttpd instances with simplistic configs:
1. first as frontend, proxying requests to backend via mod_proxy (only backend host/port are defined)
2. second as a backend (mod_magnet magnet.attract-physical-path-to). Lua script is doing only 2 things: r.req_attr["physical.path"] = $SOME_FILE and r.resp_header["X-LIGHTTPD-KBytes-per-second"] = "200"
Both instances are running locally. Trying to «download» via backend I see proper bandwidth limiting, but when I doing the same via frontend, I see the request is «hung» (wget output is «HTTP request sent, awaiting response...») for some time and after that the file is «downloaded» instantly.
Total download times (via backend and via frontend) is same more or less. Seems frontend is doing some kind of buffering before actually sending data to the client. I've tried to set server.stream-request-body to 1 or 2 but with no luck – nothing changed.
Tried 1.4.68 and 1.4.71 – no difference.
Updated by gstrauss almost 2 years ago
- Status changed from New to Invalid
- Priority changed from Normal to Low
- Target version deleted (
1.4.xx)
Stop filling issues in the lighttpd issue tracker.
The lighttpd issue track is for issues in lighttpd, not for your failure to read the documentation.
By default, lighttpd offloads requests and response from backends, as backends are often much, much slower and much, much more resource intensive.
Unexpected buffering
Nope. Expected and documented. Please RTFM before posting in the forums (see link at top labelled "Forums").
server.stream-request-body
server.stream-response-body
You should not post again to the lighttpd issue tracker (here) since you have not demonstrated the ability to distinguish your own misconfiguration from any real potential issues in lighttpd.
Future "questions" posted here by you will likely be deleted without any further response.
Also available in: Atom