Re: Cute little bug....

Chuck Murcko wrote:

> It's those experimental unc.edu servers. 8^)
>
> Aside from some child exit sluggishness when shutting down, I'm seeing
> what looks like timeouts every so often in http proxy. Probably related
> to keepalives.

What do you mean by timeouts?

> Also, the odd group of
>
> [error] (32)Broken pipe: core_output_filter: writing data to the network

What platform is this? I've been hunting down this bug for almost a week - it's been driving me nuts.

Ryan Bloom says the most likely cause is the socket being allocated from the wrong pool, but I've been checking them over and over and so far nothing. The "keepalive mismatches" are worrying me too - there should be absolutely no way for this message to ever appear when upstream keepalives are not used (such as when an HTTP/1.0 browser like Netscape v4.7 is used) and I'm seeing it now and again in the logfile.

The single only time a socket should live past the end of ap_proxy_http_handler() is when the request was successful, the upstream browser was HTTP/1.1 or higher, and there was no Connection:close.

Do you need help?

In addition to our free technical library, Pantek provides professional IT services to companies who utilize Open Source software: Learn more about Pantek's Technical Support offerings Place an order for 24/7/365 Technical Support here Learn more about Pantek, who we are, and what we do Chat with a Live Operator Related httpd.apache.org Links announce bugs cvs dev docs gui-dev modproxy-dev packagers testers Request more information about Pantek

The search continues...

Regards,
Graham

-- 
-----------------------------------------
minfrin@sharp.fm		"There's a moon
					over Bourbon Street
						tonight..."