It is the server who decides what is required to use it's services.
Hence, your proxy should obey to what the server states.
If using IIS as host, set allow anonymous access and verify that everything
works.
If so - introduce security by using WSE and sign the SOAP message itself.
This is preferred over point-to-point authentication.

Signature
rgds.
/Claus Konrad
MCSD.NET (C#)
> I want consuming a webserivce trough a proxy. I use this code.
> myService s = new myService ();
[quoted text clipped - 18 lines]
> thank you very mutch.
> Boni
Thank you for your answer, but I don't understand.
I have to pass trough a proxy to have a internet connection. The webservice
I want cosume it's outside my net.
So if I use my app to consume the same webservice on a PC with direct access
to internet I don't have problem, but I can't set the proxy on my client app
to have the same result on a PC behind a proxy.
You would say that the webservice webserver (IIS) recongnize that the call
came from a app behind a proxy instead with a direct connection so its answer
is different? And I have to change the permissions on my webserver?
best regards
Boni
> It is the server who decides what is required to use it's services.
> Hence, your proxy should obey to what the server states.
[quoted text clipped - 27 lines]
> > thank you very mutch.
> > Boni
Greg Shaw - 30 Nov 2006 10:26 GMT
Boni,
What Claus is saying is that if you can change your webservice host
so that it allows anonymous access you can check that everything
is working. If you get the same error (407) with the webservice host
set to anonymous then it is not your webservice host that has the
problem. This is just for verification.
Cheers, Greg.
> Thank you for your answer, but I don't understand. I have to pass trough a
> proxy to have a internet connection. The webservice I want cosume it's
[quoted text clipped - 43 lines]
>> > thank you very mutch.
>> > Boni