> 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.
Remember, that was a best guess, without looking at the code. I am not saying that this is the problem, just a likely place to look. Ryan _______________________________________________________________________________ Ryan Bloom [EMAIL PROTECTED] 406 29th St. San Francisco, CA 94131 -------------------------------------------------------------------------------
