* Alan Gutierrez <alan-httpd-users@xxxxxxxxx> [2005-11-17 11:42]: > * inder sabharwal <inder1@xxxxxxxxxxxxx> [2005-11-15 11:43]: > > > I have a server that sends data using Transfer-Encoding: Chunked, but > > mod_proxy is buffering up the data until it hits the internal limit of > > 8K. Our client application expects to receive data from the server over > > a period of time, and doesnot know the length of the data in advance. > > > I have looked at bugs 19954 and 34876, which claim to have fixed this in > > the latest version of apache, but apparently it is not so. I have tried > > it on the following apache servers: > > > 1.) Server version: Apache/2.0.46 > > Server built: Nov 5 2004 10:58:21 > > > 2.) Server version: Apache/2.0.55 > > Server built: Nov 15 2005 00:06:22 > > > 3.) The 2.1 beta available from apache.org. > > > Is there a patch available somewhere that I could use or a configuration > > item that I may be missing out? > > I am facing the same problem. I've tested against Apache/2.0.48. > > I'm glad to see that you've tested against other versions, and can > confirm my experience. Unfortunately, I don't have an answer for how > to fix this. I'd like to hear one. > > Is this considered a bug for a feature? I can see how it might be > benificial to buffer chunks and send them along as a larger chunk, > for some applications. > > It might be a missuse of HTTP to expect chunking to work this way, > but it would certianly make it easier on my particular application. Any progress on this? I'm getting ready to use a patched mod_proxy. Is there something like mod_push or mod_tunnel? -- Alan Gutierrez - alan@xxxxxxxxx - http://engrm.com/blogometer/ --------------------------------------------------------------------- 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
|