RE: Mem Leak when reverse proxying HTTP post requests (slightly o ff-topic)
Any chance you could take a peek at the patch I submitted for bug 19954 (HTTP tunneling through reverse proxy does not always work) as long as you are looking at that source file? BTW when I submitted the patch I bone-headedly swapped the params to diff so the changes show as '-' instead of '+' Chris Conti -Original Message- From: Cliff Woolley [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 09, 2003 4:37 PM To: '[EMAIL PROTECTED]' Subject: RE: Mem Leak when reverse proxying HTTP post requests On Tue, 9 Dec 2003, Larry Toppi wrote: I found the culprit. The EOS bucket was being removed from the brigade but not destroyed. I'm going to submit the following patch to fix this bug. *** proxy_http_old.c Tue Dec 9 16:19:52 2003 --- proxy_http.c Tue Dec 9 16:22:14 2003 That looks like a bug to me, yes... though I haven't checked the broader context in detail yet to verify. --Cliff
RE: APR_BUCKET_BUFF_SIZE question
This is the same issue I was dealing with in mod_proxy that I submitted the patch for in 'BUG 19954 [PATCH] HTTP tunneling through reverse proxy does not always work'. In my case I didn't care what the read size was, but I needed to forward on whatever had been read, even if it was less than 8000 bytes. Obviously, the patch I submitted was specific to mod_proxy, but the root issue is the same. - Chris Conti [EMAIL PROTECTED] [EMAIL PROTECTED] The buffer size is not 8K... it's 8000. 8K is what's actually allocated, ... I still don't see what problem you're trying to solve, though, by wanting a configurable buffer size? --Cliff
