httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roy T. Fielding" <field...@liege.ICS.UCI.EDU>
Subject FIN_WAIT_2 and browsermatch
Date Fri, 07 Feb 1997 01:15:26 GMT
One of the reasons people see more FIN_WAIT_2 problems with 1.2b than
with 1.1.3 is because the latter turns off keep-alive by default for
any client called Mozilla/2, whereas 1.2b requires the *addition* of
the browsermatch directive to the configuration file in order to
have the same effect.

As far as I can tell, there are no problems with the existing
lingering_close code aside from it logging a message when an ENOTCONN
is the errno from the shutdown call, which is what some OSes will
report if the client aborts the connection instead of closing it.
Systems that do not have a FIN_WAIT_2 timeout will need to disable
keepalive until such time as Microsoft and Netscape fix their clients.


View raw message