I've had this problem a few times. Especially web using 3rd party libraries that are making remote calls. Adding this to the config file seems to fix it in most instances:
<configuration> <system.net> <defaultProxy enabled="true"> <proxy usesystemdefault="True"/> </defaultProxy> </system.net> </configuration> Michael M. Minutillo Indiscriminate Information Sponge http://codermike.com On Wed, Nov 16, 2011 at 10:51 AM, Matt Siebert <[email protected]> wrote: > I should add that it seems to me that the problems are more likely the > proxy denying the request, but some of the comments I've seen recently seem > to suggest the requests aren't reaching the proxy. > > > On Wed, Nov 16, 2011 at 12:39 PM, Matt Siebert <[email protected]>wrote: > >> Hi all, >> >> I never really thought about it but just assumed that a HttpWebRequest >> would automatically discover proxy settings configured on the local machine. >> >> We're not using a proxy here but as a quick test I just configured a >> dummy proxy in IE and created a simple console app that fires off a >> HttpWebRequest, and the request did use the proxy I configured. >> >> It appears my assumption was correct for this simple scenario, but I'm >> sure there are other ways a proxy might be configured in a corporate >> environment. I still see forum posts where users complain that apps don't >> seem to use their proxy. >> >> Are there any specific coding considerations to ensure a .NET app uses >> the configured proxy? >> >> Cheers. >> > >
