SSL and port 443

Aug 14, 2009 at 2:17 AM
Edited Aug 14, 2009 at 2:21 AM

This is a repost from an Earlier Post - hoping someone has this working without proxying the tiles.

I have been tasked with moving a site using DeepEarth off port 80 for access only over SSL port 443.

While the Silverlight application runs without issue the map tiles are not coming in.

Has anyone tried this?

Coordinator
Aug 14, 2009 at 7:30 AM

I havn't but it should be possible, you will need to make sure your tiles are coming from https as well.

In fact everything should be under https or else you will have issues.

You will need to modify the Virtual Earth provider (assuming your using Bing?) to use the https version of the WCF services, these should give you a https prefix. My understanding is this will only work with a production account. Also my caching to isolated storage of this url may need to be checked to make sure it isn't caching the non https version.

For a really simple test it maybe worth setting up a really simple tile provider that just hard codes the Bing https tiles? this way you can prove it all works before dealing with requesting the token, using the https WCF service to get the path etc.

Please let us know how you go with it.

Aug 14, 2009 at 10:59 AM
thank you - I did test the https versions of the Bing Tile Servers and these are accessible but whether they accept the token for fetching the tiles might be as you said a production only requirement.

Could you go into more detail about the caching to isolated storage as potentially being issue - I can investigate that as well.

I have a need to build up my own proprietary tiles so should have opportunity to do the more simple test. First I have to create the tileserver.



From: [email removed]
To: [email removed]
Date: Fri, 14 Aug 2009 00:31:02 -0700
Subject: Re: SSL and port 443 [deepearth:65541]

From: soulsolutions
I havn't but it should be possible, you will need to make sure your tiles are coming from https as well.
In fact everything should be under https or else you will have issues.
You will need to modify the Virtual Earth provider (assuming your using Bing?) to use the https version of the WCF services, these should give you a https prefix. My understanding is this will only work with a production account. Also my caching to isolated storage of this url may need to be checked to make sure it isn't caching the non https version.
For a really simple test it maybe worth setting up a really simple tile provider that just hard codes the Bing https tiles? this way you can prove it all works before dealing with requesting the token, using the https WCF service to get the path etc.
Please let us know how you go with it.
Aug 14, 2009 at 11:00 AM

Understanding the bing maps in need of being https and possibly production account what about openstreet and yahoo? Is there an https version of them?


From: [email removed]
To: [email removed]
Date: Fri, 14 Aug 2009 00:31:02 -0700
Subject: Re: SSL and port 443 [deepearth:65541]

From: soulsolutions
I havn't but it should be possible, you will need to make sure your tiles are coming from https as well.
In fact everything should be under https or else you will have issues.
You will need to modify the Virtual Earth provider (assuming your using Bing?) to use the https version of the WCF services, these should give you a https prefix. My understanding is this will only work with a production account. Also my caching to isolated storage of this url may need to be checked to make sure it isn't caching the non https version.
For a really simple test it maybe worth setting up a really simple tile provider that just hard codes the Bing https tiles? this way you can prove it all works before dealing with requesting the token, using the https WCF service to get the path etc.
Please let us know how you go with it.
Coordinator
Aug 14, 2009 at 11:50 PM

Unlike all the other tile providers which we simply hard code, Bing Maps (formerly Virtual Earth) provides a WCF service to get the tile URL structure. As this delays the loading of the map we added some simply logic to cache the URL format to the user's local isolated storage. We don't cache the actual tiles but I certainly didn't test what would happen if you changed it to HTTPS and didn't clear this cache. To clear the cache right click and goto into the silverlight options and delete the local isolated storage.

I'm not aware of other tile providers using https, as you said in your original post you could setup a simple server side proxy.

Keep in mind that the other benifit of the Bing Maps https support is WCF services for geocoding, routes etc all under https.

Aug 15, 2009 at 2:42 AM
thank you for the information

I think you may have solved a bug that has been dogging me a while - i've fielded reports from some of my team that they bring up the application however VE tiles are not displayed while switching to OSM and Yahoo always work.
I just deleted my own silverlight isolated storage in my browser and suddenly I am now experiencing the same bug.
If you are unable to write to isolated storage what happens to the use of the VE tile server?


From: [email removed]
To: [email removed]
Date: Fri, 14 Aug 2009 16:50:32 -0700
Subject: Re: SSL and port 443 [deepearth:65541]

From: soulsolutions
Unlike all the other tile providers which we simply hard code, Bing Maps (formerly Virtual Earth) provides a WCF service to get the tile URL structure. As this delays the loading of the map we added some simply logic to cache the URL format to the user's local isolated storage. We don't cache the actual tiles but I certainly didn't test what would happen if you changed it to HTTPS and didn't clear this cache. To clear the cache right click and goto into the silverlight options and delete the local isolated storage.
I'm not aware of other tile providers using https, as you said in your original post you could setup a simple server side proxy.
Keep in mind that the other benifit of the Bing Maps https support is WCF services for geocoding, routes etc all under https.
Aug 15, 2009 at 4:58 AM
Darn - I broke something. Running fiddler I get the following

<faultcode xmlns:a="http://schemas.microsoft.com/ws/2005/05/addressing/none">a:ActionNotSupported</faultcode><faultstring xml:lang="en-US">The message with Action 'http://codeplex.com/deepearth/ITokenService/GetToken' cannot be processed at the receiver, due to a ContractFilter mismatch at the EndpointDispatcher. This may be because of either a contract mismatch (mismatched Actions between sender and receiver) or a binding/security mismatch between the sender and the receiver. Check that sender and receiver have the same contract and the same binding (including security requirements, e.g. Message, Transport, None).</faultstring>


Any help appreciated.


From: [email removed]
To: [email removed]
Date: Fri, 14 Aug 2009 16:50:32 -0700
Subject: Re: SSL and port 443 [deepearth:65541]

From: soulsolutions
Unlike all the other tile providers which we simply hard code, Bing Maps (formerly Virtual Earth) provides a WCF service to get the tile URL structure. As this delays the loading of the map we added some simply logic to cache the URL format to the user's local isolated storage. We don't cache the actual tiles but I certainly didn't test what would happen if you changed it to HTTPS and didn't clear this cache. To clear the cache right click and goto into the silverlight options and delete the local isolated storage.
I'm not aware of other tile providers using https, as you said in your original post you could setup a simple server side proxy.
Keep in mind that the other benifit of the Bing Maps https support is WCF services for geocoding, routes etc all under https.