Home/ Questions/Q 8265075
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-08T04:40:25+00:00

I am using WebClient to download some resource in following way: Stream stream; try

  • 0

I am using WebClient to download some resource in following way:

 Stream stream;
 try
 {
  WebClient webClient = new webClient();
  stream = webClient.OpenRead(MyResourceUri);
 }
 catch (Exception)
 {
  return null;
 }
 return stream;

When I do this in a WPF application, it works fine and proper stream is obtained.

When I do this in a WCF service call, it doesn’t work. A WebException is thrown with message "Unable to connect to remote server". (It works for files hosted on my machine or within company network, however it fails for any resource on web). The service is hosted on IIS7.

Investigation so far reveals the difference is because of the webproxy. The webclient.proxy in WPF application refers to the proxy settings as set in IE, whereas the one in WCF is having none.

Why is it so? And more importantly, how can I make the WebClient in WCF use similar proxy settings?

EDIT: I set the proxy on WebClient and it worked in WCF service

webClient.Proxy = new WebProxy(ProxyAddressFromIE);

Here I have hardcoded the proxy addess. What method/APIs are there to obtain one? And still why its different in WCF service & in WPF application?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    To answer one of your questions, the reason there is a difference between your WPF application and your IIS hosted WCF service is this.

    WPF applications run in an actual Windows session (your user session to be exact). This means there is a user profile loaded for that session and that session contains, amongst other things, the proxy settings as configured in IE.

    WCF services hosted in IIS do not run in a Windows session. They are run as a service and therefor do not have a Windows session (they actually run in session 0, but that’s just an implementatio detail). This means there is no proxy configuration.

    To reliably solve this, you could have your own configuration for a proxy, perhaps in web.config.
    Another option is to configure the proxy through netsh.exe.

    • 0