On Tue, Aug 02, 2005 at 10:49:59PM +0200, Kamil Srot wrote: > Joshua Slive wrote: > >Indeed you have found the problem, I believe: Range headers. In order > >to handle out-of-order range requests (which are allowed by the spec), > >httpd must buffer the entire response. Of course, that is very bad > >behavior. Instead, httpd should just ignore out-of-order range > >requests (which the spec also allows) and serve the entire thing. > > > Do you know about any will to patch this and incorporate it into stable > release? > ...maybe current behavior is good in some cases (I don't understand) but > I can imagine many people having the same problems as I do... maybe some > configuration directive can take place in case both behaviors are correct... This patch fixes the byterange filter memory consumption issue for 2.0.x: http://people.apache.org/~jorton/ap_byterange.diff Regards, joe --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|