- From: Scott Lawrence <scott-http@skrb.org>
- Date: Tue, 16 Dec 2003 10:01:42 -0500
- To: "Charumathy Venkatraman" <charumathy_v@lgsoftindia.com>
- Cc: <ietf-http-wg@w3.org>
"Charumathy Venkatraman" <charumathy_v@lgsoftindia.com> writes: > Under what conditions would a HTTP server abort a connection from the > client? > > I am testing with a server that intermittently aborts the connection. My > client fails with the error 10053 (WSAECONNABORTED). I am not able to nail > down exactly when this happens, but it seems like when I issue a POST which > the server does not support, it returns error 405 (which I am handling > fine), and the next time I issue a GET or a POST I get the 10053 error. The server is free to close the connection whenever it wants to, and it's not uncommon to see a close following an error. You might want to look at a network trace to see exactly when the TCP connection closes relative to when you are sending the next request. In any event, the client is responsible for opening a new connection whenever it needs one. -- Scott Lawrence http://skrb.org/scott/
Received on Tuesday, 16 December 2003 10:01:43 UTC