I'd grateful if someone here could let me know the motivation for the timeout parameter on the request Keep-Alive: header and the apparent choice of 300 secs as the default value. Are you expecting typical servers to keep an idle connection open for anything like that long? Nb. the response Keep-Alive: header is a different kettle of fish altogether ... clients do need a hint, both for connection pool management and for graceful handling of pipelined requests. I guess you might have added the request-side timeout on the grounds of symmetry ... but there really isn't any symmetry there: servers don't send unsolicited responses, so there's no equivalent of a client sending a request only to have it dropped because the other end has closed, but the FINs still in transit. Hmm ... actually, I'd also be very grateful for an official definition of any Netscape specific headers there might be flying around, eg. the intended semantics of Proxy-Connection: (even if it is broken ;-). Cheers, Miles -- Miles Sabin InterX Internet Systems Architect 5/6 Glenthorne Mews +44 (0)20 8817 4030 London, W6 0LJ, England [EMAIL PROTECTED] http://www.interx.com/
