Click here to Skip to main content
15,893,161 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
Hello folks!

We are trying to access a WCF Service hosted on SSL from behind a proxy(Squid) via a Silverlight Out of Browser application.

When I paste the https URL in the browser, it works fine. However, we were not able to access the service from our application. It works fine even when we try to access the service without the Squid proxy in between.

After some experimentation, we found that Silverlight issues a Windows Security dialog for proxy authentication whenever we access a HTTP service from an OOB application, but does not show any dialog for an HTTPS service, hence returning a 407 Proxy authentication required when seen from Fiddler.

As a workaround, we found that using the Client http stack for all HTTPS requests shows the Windows Security dialog that was working only for HTTP requests earlier.

Usage for client http stack ---> WebRequest.RegisterPrefix("https://", WebRequestCreator.ClientHttp);

It does not seem to be a cross domain or client access policy issue since we are able to access the HTTPS service without the Squid Proxy in between.

So the question is -- why are we receiving the Windows Security dialog when a HTTP request is fired via the Browser Http stack but not when a HTTPS request is fired via the Browser Http stack? Or, what is the Client Http Stack doing differently that it is showing the dialog for both HTTP and HTTPS requests?

We couldn't find any information on what Client Http does differently as compared to Browser Http wih respect to handling HTTPS requests to WCF services.

It would be awesome if someone could help!

Thanks

Pulkit
Posted

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900