Hi Roland, > What happens if you access the page from curl or wwwget? Do you get the content you want, or the same error as when using HttpClient? No exception with wget or HTTPClient now (Appears the site has been fixed).
There are other public URL's with same slow download speed, so I guess the exception is not the real cause of slow down. > It's been mentioned before: you will have to use some network sniffer tool like Wireshark to capture a request that returns the content you want. Then we can compare that request with the one HttpClient sends. Uploaded two Wireshark log files with IE and HttpClient 3.1. From my novice view (looking at a sniffer log first time), there appears to be a problem with DNS resolution at my end. Will work on the same in parallel. Thanks -- View this message in context: http://www.nabble.com/Performance-Issues-with-Transfer-Encoding-chunked-tp14106574p14418943.html Sent from the HttpClient-User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
