On Thu, Apr 26, 2007 at 04:56:46PM +0300, Eugeny N Dzhurinsky wrote: > Hello! > > I understand something might be wrong for the website and the protocol might > be corrupted, but as soon as mozilla/IE browsers are displaying the website > fine, we need to get some workaround. Could you please suggest something, > which will not lead us to modifying Httpclient sources? > > I've read about error handling for protocol errors, but I just found it is > possible to force HttpClient to retry this url again and again. In such case > as described above this will lead to a infinite loop unless we will still > handle this error (which isn't an error in our case). > > We are using HttpClient 3.01 and 3.1-RC1, with same results.
So is there some kind of a non-intrusive workaround for resolving such errors in HttpClient? Thank you in advance. -- Eugene N Dzhurinsky --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
