[EMAIL PROTECTED] wrote: > Hello: > Actually, I just found that this is defined in > the RFC (probably to prevent DOS attacks): > > 8.2.2 Monitoring Connections for Error Status Messages > http://www.w3.org/Protocols/rfc2616/rfc2616-sec8.html#sec8.2.2 > > "An HTTP/1.1 (or later) client sending a > message-body SHOULD monitor the network connection > for an error status while it is transmitting the > request. If the client sees an error status, it > SHOULD immediately cease transmitting the body. If > the body is being sent using a "chunked" encoding > (section 3.6), a zero length chunk and empty trailer > MAY be used to prematurely mark the end of the > message. If the body was preceded by a Content-Length > header, the client MUST close the connection."
That explains may guesses. > > If this is not the current behaviour of the > HttpCli component, then perhaps we can work in > implementing this. I don't think it's current THttpCli's behaviour. How to handle authentication methods depending on keep-alive with POST, if the connection has to be dropped? -- Arno Garrels -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be