Posted By: Mike Taulty | Jul 15th, 2008 @ 7:05 AM | 8,648 Views | 6 Comments
There are limitations for calling web services over HTTPS in Beta 2. Here, we look at what we can do with respect to calling web services over HTTPS.
Media Downloads:
Rating:
0
0

Great video but... it doesn't work.

Made "exactly" the changes you demonstrated in the video. But it simply doesn't work.

I'm using VS2008 SP1,
Framework 3.5SP1,
SilverLight 2.0 Beta2.
The IIS 6 has only one domain baseadress for the WCF services. The IIS server are SSL enabled and are running .NET webservices along side. The service you demonstrated are working fine under http.

When making the changes and rebuilding the project and post to the server the client can't speak with the WCF.svc.
However the client can run under SSL and the WCF.svc is also visible in browser and when updating the servicereference in VisualStudio.
But the client can't communicate with it dispite the changes in the servicereferense and changes to the binding in the hosting site web.config.

Seems much harder to get SSL working with WCF than with the old .NET Webservices ;O).

Hi Mike, Great series for noobs!

Do WCF HTTPS calls still have to come from an HTTPS SL App in SL2.0 RTW?

I noticed that you are making your calls in a single domain. Can SL do cross domain HTTPS?

Thanks,
Mark

Hm - I was looking forward to this video hoping to get my solutions, but... Has the video been removed???? I can click nothing

what's the deal here? why was this video removed?

it's a very useful source of information for silverlight devs.

please reinstate it as quickly as possible.

thx

Microsoft Communities