Bug #663
closedmod_proxy doesn't stream data ?
Description
I didn't check the source code but it seems like mod_proxy is trying to cache the whole page before sending it back to the browser.
This is not a problem for small pages but when you have a multipart jpeg stream that never ends, it explodes memory consuption. Also, when the browser is closed, netstat shows me that lighttpd still tries to get the data from the source host.
I know this is not a standard usage case of lighttpd. Is it possible to stream the data to the browser instead of keeping it until the end of page ? I think it would be better but I'm not an HTTP expert.
Cheers,
zimbatm
-- zimbatm
Updated by Anonymous over 17 years ago
I have found that this is a problem for me as well. The cgi script on the target system is writing critical output real-time, but nothing can be seen until the script has finished.
-- jschmier
Updated by Anonymous over 17 years ago
Replying to jschmier:
I have found that this is a problem for me as well. The cgi script on the target system is writing critical output real-time, but nothing can be seen until the script has finished.
real problem is that if you for any stupid reason serving big files from application server and using mod_proxy to communicate between two of them, in that case it's very easy to exploit dos on lighttpd by connecting once and:
while (1) {
get /largefile.extension
}
in 2 minutes lighttpd will be eating 80% of your server ram...
Updated by jan over 17 years ago
- Status changed from New to Assigned
This is known and fixed in the upcoming 1.5.0 release.
Updated by clsung over 17 years ago
This problem also happpens when I use subversion/mod_proxy/apache to check out large repository ( 931Mb )
Updated by jwmcglynn about 17 years ago
- Status changed from Assigned to Fixed
- Resolution set to duplicate
Since this was moved to 1.5 this is practically a copy of #1069, which includes a patch for mod_proxy_core.
Also available in: Atom