Oleg Kalnichevski wrote:
Siddhartha,
I believe the solution to this problem is trivial. All it takes is checking for availability of a response from the target server prior to sending each consecutive chunk of request body. A premature response from the target server detected before the request body has been transmitted in its entirety most likely signifies a problem (such as authentication failure), which should cause the request to be aborted and the connection force-closed once the response is read.
I just want to note that this approach may interfere with a future implementation of HTTP pipelining.
Odi
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
