c# Webrequest through https (configured) proxy (The ServicePointManager does not support proxies of https scheme) RRS feed

  • Question


    Here seemes to be a better place, than stackoverflow. I would like a MSFT to again target this very important question. Or at least point to a working solution. THANK YOU

    I need to connect to a https-url by using a proxy which also has a https address. My code is simply like this:

    var webRequest = (HttpWebRequest)WebRequest.Create("");
    var proxy = new WebProxy(new Uri("https://proxyaddress:port"));
    webRequest.Proxy = proxy;
    WebResponse webResponse = webRequest.GetResponse();

    Doing this I get a well known Error:

    The ServicePointManager does not support proxies of https scheme

    No credential-code here for simplicity. And no, the users will not change the proxy to http.

    Now there are some hints, that this cannot be achieved like: Microsoft blog or MSDN forum but these are all a little old and this states, that at least Chrome and Firefox seem to have a solution to that issue.

    Can anyone tell me, how to get to a https address through a proxy which itself can only be reached through https?

    The ServicePointManager should be able to do this by now, is there some development?


    JEns D.

    Monday, July 10, 2017 1:04 PM

All replies

  • Hi Jens D.,

    >>The ServicePointManager should be able to do this by now, is there some development?

    According to your description and error message, I create a simple demo by using Webrequest and WebClient with .net framework 4.7, all throw the exception.  and we could not achieve it via Webrequest and https proxy.

    it seems that it support TCP, like this:

    In addition, I would suggest that you could post a feedback on the following link.

    Best regards,

    Cole Wu

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact

    Tuesday, July 11, 2017 3:03 AM
  • I'd like to follow up on this. Connect.Microsoft.Com is discontinued. But I still have no solution to this problem. Https-Proxies are not rare anymore.

    What is the best practise in my case? 

    The first link in your answer is to create a Proxy - right?

    JEns D.

    Wednesday, March 27, 2019 1:08 PM