DZ-Jay wrote: >> It works when you send all data in FSendStream from event >> THttpCli.SocketDataSent at once. That's of course not a real fix but >> it works, give it a trial. > > This works because it prevents the HttpCli from acknowledging the 401 > response until after it finishes sending (am I right?).
Yes, because all body data is in THttpCli's internal send buffer yet when the 401 is received. > I suggest making the same tests but with a very large file (some > megabytes at least), and see how IE handles such cases (I want to see > if there is any heuristicts in IE that would cause it to drop a > connection if the file is too big, so that it doesn't waste > resources). Both IE and FireFox sent 2MB twice, they dig not drop the connection. > If it does exactly the same thing as we have seen, then > we should try to replicate the behaviour in HttpCli: perhaps adding a > new machine state that instead of re-sending when 401 is detected, it > makes sure that the body has been sent completely, and if not, it > delays re-sending until it does. Implementation won't be easy, otherwise Maurizio would have fixed it already. -- 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
