By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,948 Members | 1,595 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,948 IT Pros & Developers. It's quick & easy.

HTTP Proxy authentification problem

P: n/a
My first post on this newsgroup as I have a very strange problem with a WSE
client trying to access a .NET WS through a secured HTTP Proxy : it is woking
with HTTPS but not with HTTP ?! I am really talking about the same code and
only changing the server url.
The problem is due to the HTTP proxy authentification but we don't
understand why. Using EtherReal, we can see in both cases that the WS client
is trying to access the server and is receiving a HTTP 407 from the proxy.
But then, there is a major difference :
- when using HTTPS, the WSE client is sending credentials and everything is
- when using HTTP, nothing happens : it seems that the WSE client is not
sending anything : we have a 100 seconds gap between the HTTP 407 and the
first WSE client action (timeout). We finally get a timeout exception.

When using HTTPS url, we can use a very simple line of code and it is
working perfectly well :
ws.Proxy = new WebProxy(new Uri(proxyURL),true,null, new
NetworkCredential(login, pwd));

Now, we tried this code but we got the same result :
ws.Proxy = WebProxy.GetDefaultProxy();
CredentialCache cc = new CredentialCache();
cc.Add(new Uri(proxyURL),"Basic",new NetworkCredential(login,pwd));
ws.Proxy = new WebProxy(new Uri(proxyURL),true,null,cc);

Hope someone can help us ...

Dec 23 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.