MS Soap Toolkit 3 - Proxy Server Issue

Cameron Michaelson

unread,

Jun 4, 2003, 10:08:42 AM6/4/03

to

I am trying to use the MS Soap Toolkit 3.0 API's to query
an external web service (resides outside my companies
firewall) and have used every combination of proxy
settings within the soap api's without any luck. Can some
please send me a snippet of code (THAT WORKS!) for
configuring the MS Soap Tookit 3 to poke past my proxy
server (requires credentials).

Thanks a million!
Cameron

Gerson Rolim

unread,

Jun 17, 2003, 11:18:41 AM6/17/03

to

Sorry to tell you that, but this is the answer I recept
from MS Premier Support. Hope your proxy is MS, Netscape
or Apache:

Hello Sir, I reviewed the netmon cap files more closely.
One of the things that I noticed is the proxy server
involved in this is: SQUID/2.4

After searching in our bug database for soaptk, I found
that developer group is aware of this scenario where
soaptk clients on win98 and winme machine fail when SQUID
proxy is involved. The same client works on win2k and
winxp. They have clearly stated that this is not going to
fixed. They have also issued a list of supported proxies
and respective configuration by soap toolkit v3.0 Please
note that a KB article is currently in works which
documents following:

Following Proxy scenarios are tested/supported by SOAP
Toolkit 3.0:

MS ISA Proxy
o Proxy: no auth, NTLM auth
o Tunneling: plain http connections, SSL
connections, authenticated (Basic, Digest, NTLM)
connections
MS Proxy 2.0
o Proxy: no auth, Basic auth
o Tunneling: plain http connections, SSL
connections, authenticated (Basic, Digest) connections
Apache Proxy
o Proxy auth: no auth, basic auth
o Tunneling: plain http connections,
authenticated(Basic) auth
Netscape Proxy Unix v3.52
o Proxy: no authentication
o Tunneling: plain http connections

>.
>

JT

unread,

Jun 18, 2003, 9:42:33 AM6/18/03

to

Hi Gerson,

Thanks for posting this information. The message from MS is unclear as to
connecting through SQUID would work when connecting with a win2k/xp client.

Did you get it working, with *any* proxy requiring authentication? I noticed
in the original email that Cameron was asking for a code snippet -- did you
get that? If so, it'd be great to post that as well.

Thanks,
JT

"Gerson Rolim" <ger...@supplysystems.com.br> wrote in message
news:153601c334e3$bc2e5740$a501...@phx.gbl...

Gerson Rolim

unread,

Jun 20, 2003, 4:21:12 PM6/20/03

to

Hi JT!!!
It was really a pleasure to post this info, because I was
looking for it since May w/o any clue... So, when MS told
me its position about the issue, I thought it'd be
important to share it with you all... :)
Well, in my case, we discovered that Win98 and WinMe have
some problems in an environment involving soaptk and a
non-supported Proxy Server (anything different from MS
Proxy, MS ISA, Netscape and Apache)... As you can see, MS
won't correct this bug, in these OSes versions...
However, we had no problems with WinNT, Win2k and WinXP...
Here is the code we used, that worked with MS newer OSes
versions and with the older ones in networks using
supported proxies:
---

set sc = new SoapClient30

sc.MSSoapInit "c:\file_path\ACME.xml"

'Proxy user properties
sc.ConnectorProperty("ProxyServer") = "server addr:8080"
sc.ConnectorProperty("ProxyUser") = "userlogin"
sc.ConnectorProperty("ProxyPassword") = "password"

-----
Cheers,
Gerson Rolim
SupplySystems
Brazil

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

>.
>

Roger

unread,

Oct 14, 2003, 10:29:18 PM10/14/03

to

I am having similar issue too. We can't get MS Soap Toolkit 3.0 to connect
to an external .NET webservice through proxy server as we've been having
error "0x800A151E". Internet Explorer proxy settings has been configured
properly (able to browse web pages) but MS Soap does works. Any clue? By the
way, MS Soap3 doesn't seems to support ConnectorProperty "UseProxy", and
"ProxyPort" as it gives me the error "Connector: The property "ProxyPort" is
not recognized. HRESULT=0x800A1388". Any help will be greatly appreciated!
Thanks!

"Cameron Michaelson" <cameron.m...@wal-mart.com> wrote in message
news:37cc01c32aa2$cdb9f2d0$3101...@phx.gbl...

Des Browne

unread,

Nov 23, 2003, 11:30:23 PM11/23/03

to

I am using the following bit of code to set the User Agent and ensure that
Internet Explorer's default proxy settings for the current user are being
used.

Dim oSoapClient
Set oSoapClient = CreateObject("MSSOAP.SoapClient30")
oSoapClient.MSSoapInit "http://SERVER/service.asmx?wsdl"
oSoapClient.ConnectorProperty("ProxyServer") = "<CURRENT_USER>"
oSoapClient.ConnectorProperty("EnableAutoProxy") = TRUE
oSoapClient.ConnectorProperty("RequestHTTPHeader") = "user-agent:
Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.1.4322)"

There seems to be no information I can find about RequestHTTPHeader anywhere
on the internet and only the following in the help file.

RequestHTTPHeader (write only) Enables you to set HTTP header for
the request message.

but it seems to work by setting just the property you want to change and
letting the Toolkit fill in the rest.

hope this helps.

- Des

"Roger" <roger...@NOSPAMwebxcentric.com> wrote in message
news:eBVqSQsk...@TK2MSFTNGP12.phx.gbl...