> Probably a solution could be to expose the FRequestDoneError field. > The status code should be meaningful only if FRequestDoneError=0.
You mean reporting 10060 (and others) to the error field ? Yes, probably good. But statuscode must still return 404 otherwise probably a lot of existing application code would be broken ! -- [EMAIL PROTECTED] http://www.overbyte.be ----- Original Message ----- From: "Maurizio Lotauro" <[EMAIL PROTECTED]> To: <twsocket@elists.org> Sent: Sunday, April 17, 2005 12:00 AM Subject: [twsocket] HttpCli and the 404 status code > Hello, > > I noticed that the HttpCli component return the 404 status code not > only when the server return this code but even under different > situations. For example when it is unable to resolve the hostname or > when wsocket raise an error (please correct me if I'm wrong). > > This is a problem because the application is unable to distinguish > if this error is returned by the server or not. > > In a program I implemented a very simply retry mechanism. The retry > will be executed only if the status code returned is not a permanent > error (I identified the 408, 503 and 504). The 404 is a permanent one > but it is returned even when the socket return 10060 (Connection > timed out). > > Probably a solution could be to expose the FRequestDoneError field. > The status code should be meaningful only if FRequestDoneError=0. > > What do you think? > > > Bye, Maurizio. > > > -- > To unsubscribe or change your settings for TWSocket mailing list > please goto http://www.elists.org/mailman/listinfo/twsocket > Visit our website at http://www.overbyte.be > -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
