ThinkGeo.com    |     Documentation    |     Premium Support

Web API locate requirements and limitations

#1

Hi,
I’m attempting to prototype a mobile Web page “application” based on ThinkGeo and Bing Maps. I’ve used the Layers sample and can display the map. I’ve used the GettingStarted sample to include a button triggering current location. This works fine, on localhost, using http (Bing maps loads, etc.). It does not work with https, on localhost. I feel like I’m missing a list of steps to actually configure a workable Web-based location application or a list of limitations describing why my current attempts don’t work right.

Does anyone possess a sample showing a working Leaflet or OpenLayers-based useful tracking application? I’m not sure at this point whether the problem is project settings or something else.

Fiddler has not given any insights; when using https, it simply reports that the connection was reset when the Web API launch page was loaded.
Thanks,
Paul T.

#2

Hi Paul,

It looks we don’t need to do any special things for https on map. You can view our online sample https://maps.thinkgeo.com/, it also is https and it works.

If the map don’t works under https, have you get any error information? Does the map shows blank or many pink tiles? Could you get the tile image and render it on map? A sample project or test pages should be helpful to let us understand more about your scenario.

Regards,

Don

#3

I’ve tracked down the HTTPS issue. There’s a bug in the Visual Studio 2017 15.3.3 version of IIS Express. Not sure the exact nature of the bug, but Microsoft confirms a fix will be coming. Installing the IIS Express v. 10 from the Microsoft Web site instead works fine. Will send my other questions in a new thread :wink:

#4

Hi Paul,

I am glad to hear that works.

Regards,

Don