Browse Source
When lighttpd is not configured to stream the response body, lighttpd sends partial content with an incorrect Content-Length to an HTTP/1.0 client if a backend sends Transfer-Encoding: chunked in response to lighttpd HTTP/1.1 request (to backend), and the response from the backend ends up truncated. lighttpd could instead send an HTTP/1.0 502 Bad Gateway, but the current implementation chooses to send the partial content. After all, an HTTP/1.0 client is, well, HTTP/1.0, and so of limited intelligence.master
1 changed files with 38 additions and 0 deletions
Loading…
Reference in new issue