Security warning message while accessing as a https in Javascript API

[PravinAress]

Hello,

I have used nokia map URL as <script type="text/javascript" charset="UTF-8" src="https://api.maps.nokia.com/2.2.3/jsl.js?with=all"></script>

If I access my site using https then it giving security warning message as "The web page contains the content that will not be delivered using a secure https connection which could comprimise the security of entire web page"

Please let me know the reason of this warning

Thanks

[wizard_hu_]

At the first glance there seem to be a plain http reference inside the script. But I am not familiar with the maps API, for example I do not know if you are really obliged to get a simple JavaScript file via https.

[PravinAress]

Thank you for reply.
But really needs the any reference or solution to resolve this problem.

[MServices]

Hello,
Your question may not clear.Where you use.Is it in mobile browser or desktop browser.I assume mobile browser.

The mobile browser(webkit engine) may not support secure connection, I am not sure because I have not tried but I have heard.The concept behind is TCP connection support https connection whereas (browser)webkit may not have secure layer.

[hamishwillee]

Moved thread - you might get more feedback from the maps team since you're accessing the maps API.

[jasfox]

I have used Nokia map URL as <script type="text/javascript" charset="UTF-8" src="https://api.maps.nokia.com/2.2.3/jsl.js?with=all"></script>
If I access my site using HTTPS then it giving security warning message as "The web page contains the content that will not be delivered using a secure HTTPS connection which could compromise the security of entire web page"
Please let me know the reason of this warning

The script you are using is the basic Nokia Maps API , rather than the enterprise version. As can be read on this thread, the basic API does not support HTTPS - hence the map tiles are coming through as HTTP, and your app is complaining about the mix.

There are two potential fixes for this - the cheapest fix would be to continue to use the basic API, but make the page request HTTP. The alternative would be to upgrade to the enterprise API - to obtain it you will need to Request a custom package with more features at the bottom of the plans page