[OpenStreetMap] #5298: Request to https-embeded-Map (Mapquest) not fully https

[OpenStreetMap]

#5298: Request to https-embeded-Map (Mapquest) not fully https
------------------------+-------------------------------------------------
  Reporter:  netty4711  |      Owner:  rails-dev@…
      Type:  defect     |     Status:  new
  Priority:  minor      |  Milestone:
 Component:  website    |    Version:
Resolution:             |   Keywords:  export, embed, ssl, https, mapquest
------------------------+-------------------------------------------------

Comment (by netty4711):

 "forcing" is a hard word from me. Sorry for that. But there are some
 hints, that many websites would change in near future to https-version.
 Google is now going to promote https as it gaves https websites a higher
 ranking: http://googlewebmastercentral.blogspot.de/2014/08/https-as-
 ranking-signal.html

 Next step seems to warn user on a non-https site in Google Chrome and if
 this happens other browsers would also do this:
 http://www.bbc.com/news/technology-30505970
 http://www.chromium.org/Home/chromium-security/marking-http-as-non-secure

 Same changes happens at the moment with mobile/non-mobile sites:
 http://www.business2community.com/online-marketing/google-start-
 penalizing-non-mobile-sites-01175992

 But to come back to the issue. If a site has user login functionality it
 is very often also a ssl-secured site. Most sites uses than everywhere
 https. Than there are problems with embeding Maps with the standard
 feature.

 Thanks for looking at that.

--
Ticket URL: <https://trac.openstreetmap.org/ticket/5298#comment:2>
OpenStreetMap <http://www.openstreetmap.org/>
OpenStreetMap is a free editable map of the whole world