Slow Http client calls from ASP.NET 2.0 Make sure you check your Proxy Settings!

Posted by: Rick Strahls WebLog, on 14 Dec 2005 | View original

I posted about this issue before indirectly, but I think it bears repeating as a dedicated topic. I've seen a fair number of questions about this on various forums recently.    The problem: You're using some sort of HTTP client from an ASP.NET 2.0 or low rights .NET 2.0 application and it's very slow to connect to a Web server to retrieve HTTP content. This could be with WebRequest, WebClient, XmlDom/Reader or a Web Service Client.   In .NET 2.0 the default proxy configuration...

Advertisement
The leading UI suite for ASP.NET - Telerik radControls
Outstanding performance. Full ASP.NET AJAX support. Nearly codeless development.

Similar Posts

  • ClientBlocker 1.1 more
  • Free MSDN Training Events in Your Area more
  • Securing Site Content/Images more
  • Free MSDN Training Events in Your Area more
  • Planning Party with Palermo 2006 @ Tech Ed - level 000 more
  • TradeMe Sale... Media rumble Fairfax v ACP... NZ Website Rankings more
  • HttpMappingMode.Soap vs HttpMappingMode.AnyXml vs MapAddressingHeaderToHttpHeaders=true more
  • FREE CMS System for ASP.NET 2.0 more
  • TradeMe starting to run on ASP .NET more
  • Free Enterprise CMS for Microsoft .NET Framework 2.0 and ASP.NET 2.0 released! more

News Categories

.NET | ADO.NET | Agile | Ajax | Architecture | ASP.NET | BizTalk | C# | Certification | Community Server | dasBlog | DataGrid | DataSet | Debugger | DotNetNuke | Events | GridView | IIS | Indigo | JavaScript | Mobile | Mono | Patterns and Practices | Performance | Podcast | Refactor | Regex | Security | Sharepoint | Silverlight | Smart Client Applications | Software | SQL | VB.NET | Visual Studio | W3 | WCF | WinFx | WPF | WSE | XAML | XLinq | XML | XSD