ServicePointManager does not support proxies of HTTPS scheme

[Molina]

Hi !!!

I have a VB.Net application that consumes an WebService. The problem is that
the HTTP address works fine, but it will change to an HTTPS address, and it
isn't working.

The weird thing is that I could add the WebReference and view the WSDL in my
browser (even in my iPaq Internet Explorer) without any problem, when I try
to consume the WebService I get the following error message: "The
ServicePointManager does not support proxies of https scheme."

What causes this error? How can I fix it or workaround?
Why I can add the WebReference and cannot consume the WebService?

Thanks in advance,

--
Carlos Molina

[Dan Rogers]

Hi Carlos,

When you use TLS, the browser typically switches to port 443. The WSDL
request (add web reference) goes over HTTP get, and I suspect is directed
in your case over port 80.

It would seem that you are routing through a proxy server that does not
support port 443 operations. I think the only remedy would be to switch to
a router that does support secure sessions. There may be an administrative
option that your IT department has set to prevent them from not being able
to monitor secure traffic.

I hope this helps

Dan Rogers
Microsoft Corporation
--------------------
Thread-Topic: ServicePointManager does not support proxies of HTTPS scheme
thread-index: AcTZP/eIcgF4orGMQFGumXnQqNFqfw==
X-WBNR-Posting-Host: 200.99.5.146
From: =?Utf-8?B?TW9saW5h?= <Mo****@discussions.microsoft.com>
Subject: ServicePointManager does not support proxies of HTTPS scheme
Date: Fri, 3 Dec 2004 05:57:03 -0800
Lines: 18
Message-ID: <37**********************************@microsoft.co m>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups: microsoft.public.dotnet.framework.webservices
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
Path: cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFT NGXA03.phx.gbl
Xref: cpmsftngxa10.phx.gbl
microsoft.public.dotnet.framework.webservices:7790
X-Tomcat-NG: microsoft.public.dotnet.framework.webservices

Hi !!!

I have a VB.Net application that consumes an WebService. The problem is
that
the HTTP address works fine, but it will change to an HTTPS address, and it
isn't working.

The weird thing is that I could add the WebReference and view the WSDL in
my
browser (even in my iPaq Internet Explorer) without any problem, when I try
to consume the WebService I get the following error message: "The
ServicePointManager does not support proxies of https scheme."

What causes this error? How can I fix it or workaround?
Why I can add the WebReference and cannot consume the WebService?

Thanks in advance,

--
Carlos Molina

[Molina]

Hi, Dan!

Thanks for your answer.

I told about your answer to our network administrator and he didn't figured
how we could do it, because we've tried the solution suggested in the
following article
(http://support.microsoft.com/default...b;en-us;283284) to allow
secure requests through a port different than 443, but the error message
still the same...

I'm not sure if the solution from the article above applies to our proxy or
the WebService owner's proxy... Am I making a mess?

Thanks again!
"Dan Rogers" wrote:

Hi Carlos,

When you use TLS, the browser typically switches to port 443. The WSDL
request (add web reference) goes over HTTP get, and I suspect is directed
in your case over port 80.

It would seem that you are routing through a proxy server that does not
support port 443 operations. I think the only remedy would be to switch to
a router that does support secure sessions. There may be an administrative
option that your IT department has set to prevent them from not being able
to monitor secure traffic.

I hope this helps

Dan Rogers
Microsoft Corporation
--------------------

[Dan Rogers]

Hi,

I think the term proxy is what is adding some confusion. There is an HTTP
proxy server somewhere in your environment that is saying it will not pass
SOAP requests. This isn't the "proxy" that is generated to make the call
from the client program - even though the word is the same (It's meaning is
applicable to both types of proxies). You need to find the admin of your
intranet, and see if you can get them to grant SOAP permissions in their
proxy server infrastructure.

Dan
--------------------
Thread-Topic: ServicePointManager does not support proxies of HTTPS scheme
thread-index: AcTbjg1ZZcQO/wciSkaOwbYlw/fHNA==
X-WBNR-Posting-Host: 200.99.5.146
From: =?Utf-8?B?TW9saW5h?= <Mo****@discussions.microsoft.com>
References: <37**********************************@microsoft.co m>
<gZ**************@cpmsftngxa10.phx.gbl>
Subject: RE: ServicePointManager does not support proxies of HTTPS scheme
Date: Mon, 6 Dec 2004 04:21:02 -0800
Lines: 36
Message-ID: <4C**********************************@microsoft.co m>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups: microsoft.public.dotnet.framework.webservices
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
Path:
cpmsftngxa10.phx.gbl!TK2MSFTFEED01.phx.gbl!TK2MSFT NGP08.phx.gbl!TK2MSFTNGXA0
3.phx.gbl
Xref: cpmsftngxa10.phx.gbl
microsoft.public.dotnet.framework.webservices:7888
X-Tomcat-NG: microsoft.public.dotnet.framework.webservices

Hi, Dan!

Thanks for your answer.

I told about your answer to our network administrator and he didn't figured
how we could do it, because we've tried the solution suggested in the
following article
(http://support.microsoft.com/default...b;en-us;283284) to allow
secure requests through a port different than 443, but the error message
still the same...

I'm not sure if the solution from the article above applies to our proxy or
the WebService owner's proxy... Am I making a mess?

Thanks again!
"Dan Rogers" wrote:

Hi Carlos,

When you use TLS, the browser typically switches to port 443. The WSDL
request (add web reference) goes over HTTP get, and I suspect is directed
in your case over port 80.

It would seem that you are routing through a proxy server that does not
support port 443 operations. I think the only remedy would be to switch to a router that does support secure sessions. There may be an administrative option that your IT department has set to prevent them from not being able to monitor secure traffic.

I hope this helps

Dan Rogers
Microsoft Corporation
--------------------

[TobyRiley]

Did you find a solution to this problem. As i have same issue - see my new
post (SSL Web Service Proxy Authentication)

Thanks

Toby
"Dan Rogers" wrote:

Hi,

I think the term proxy is what is adding some confusion. There is an HTTP
proxy server somewhere in your environment that is saying it will not pass
SOAP requests. This isn't the "proxy" that is generated to make the call
from the client program - even though the word is the same (It's meaning is
applicable to both types of proxies). You need to find the admin of your
intranet, and see if you can get them to grant SOAP permissions in their
proxy server infrastructure.

Dan
--------------------
Thread-Topic: ServicePointManager does not support proxies of HTTPS scheme
thread-index: AcTbjg1ZZcQO/wciSkaOwbYlw/fHNA==
X-WBNR-Posting-Host: 200.99.5.146
From: =?Utf-8?B?TW9saW5h?= <Mo****@discussions.microsoft.com>
References: <37**********************************@microsoft.co m>
<gZ**************@cpmsftngxa10.phx.gbl>
Subject: RE: ServicePointManager does not support proxies of HTTPS scheme
Date: Mon, 6 Dec 2004 04:21:02 -0800
Lines: 36
Message-ID: <4C**********************************@microsoft.co m>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups: microsoft.public.dotnet.framework.webservices
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
Path:
cpmsftngxa10.phx.gbl!TK2MSFTFEED01.phx.gbl!TK2MSFT NGP08.phx.gbl!TK2MSFTNGXA0
3.phx.gbl
Xref: cpmsftngxa10.phx.gbl
microsoft.public.dotnet.framework.webservices:7888
X-Tomcat-NG: microsoft.public.dotnet.framework.webservices

Hi, Dan!

Thanks for your answer.

I told about your answer to our network administrator and he didn't figured
how we could do it, because we've tried the solution suggested in the
following article
(http://support.microsoft.com/default...b;en-us;283284) to allow
secure requests through a port different than 443, but the error message
still the same...

I'm not sure if the solution from the article above applies to our proxy or
the WebService owner's proxy... Am I making a mess?

Thanks again!
"Dan Rogers" wrote:

Hi Carlos,

When you use TLS, the browser typically switches to port 443. The WSDL
request (add web reference) goes over HTTP get, and I suspect is directed
in your case over port 80.

It would seem that you are routing through a proxy server that does not
support port 443 operations. I think the only remedy would be to switch

to

a router that does support secure sessions. There may be an

administrative

option that your IT department has set to prevent them from not being

able

to monitor secure traffic.

I hope this helps

Dan Rogers
Microsoft Corporation
--------------------