[In order for any reply to be added to the PR database, ] [you need to include <[EMAIL PROTECTED]> in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [automatically because of the potential for mail loops. ] [If you do not include this Cc, your reply may be ig- ] [nored unless you are responding to an explicit request ] [from a developer. ] [Reply only with text; DO NOT SEND ATTACHMENTS! ]
Synopsis: timeout values need better logic State-Changed-From-To: suspended-closed State-Changed-By: fielding State-Changed-When: Sun Sep 13 17:16:14 PDT 1998 State-Changed-Why: The timeout logic was fixed a long time ago. The inter-request timeout is different from the first-request timeout because the application round-trip is subject to more Internet rerouting sillyness than the later requests, and also because it makes it easer to debug using TELNET. The timeout period is now reset to a full hard_timeout as soon as the request_line is read, which solved the problem originally reported.
