Zum Hauptinhalt gehen

As of iOS 10, Safari now requires HTTPS for Geolocation

Permanently deleted user
As you may recall, Google began requiring HTTPS for "powerful features" -- including geolocation -- (https://support.geocortex.com/essentialsGSCForum?sub-nav=forum&main-nav=essentials&id=906600000000BdyAAE) in Chrome version 50 back in April of this year . With the release of iOS 10 last week, Apple has followed suit: (https://developer.apple.com/library/content/releasenotes/General/RN-iOSSDK-10.0/) Safari now also requires HTTPS for geolocation : "WebGeolocation now requires a secure (HTTPS) website to work on both iOS and macOS to prevent malicious use of location data."

 

If you are using geolocation in your viewer applications, you are likely already using HTTPS, but if not, we urge you to consider securing your applications to prevent users from seeing errors like the one shown here:

 

_img_ alt="Error shown in Safari when attempting to use geolocation over HTTP: "There was an error in geolocation: Insufficient permissions for geolocation." src="https://latitudegeo--c.na53.content.force.com/servlet/rtaImage?eid=90660000000PDgr&feoid=Body&refid=0EM60000000HSIV"_/_img_

 

If you cannot secure your application, or geolocation is not necessary to your application, we recommend removing geolocation from the user interface of your viewer applications. More information on that can be found in (https://support.geocortex.com/essentialsGSCForum?sub-nav=forum&main-nav=essentials&id=906600000000BdyAAE) the previous announcement for Chrome 50 .
0

Kommentare

12 Kommentare

Datum Stimmen
  • Permanently deleted user
    Hi Jordan,

     

    We are using geolocation in our viewer applications without securing it, and we got this error on IOS10. is this there any fixes in the next GVH release? We need this feature and we don’t plane to use the https in the near future.

     

    Thanks,

     

    Ahmad

     

     
    0
  • Permanently deleted user
    Ahmad,

     

    We are in the same situtation as you and I see you post is a month old. Did you find a alternate solution?

     

    Thanks

     

    Steve
    0
  • Permanently deleted user
    Hello Ahmad and Steve,

     

    I'm sorry to say that as these changes are coming from the web browser, and not the HTML5 viewer, this is not something that we can fix.  It's worth noting that this change is arguably a good one.  You don't want to be serving an application that is broadcasting your user's physical locations in clear text.  HTTPS helps prevent this.  

     

    If you have any followup questions or concerns, please let me know!

     

    Thanks,

     

    Danny
    0
  • Permanently deleted user
    Hi Daniel,

     

    As Ahmad and Steve said , Do you have any solution for this issue? or could you make the HTML5 viewer compatable with web browser without any changes?

     

    We can stay as we are (without secure our application) and we would to activate this feature.

     

    Thank you in Advance,

     

    Fatin
    0
  • Permanently deleted user
    Hi Fatin,

     

    As I mentioned, this is not something we can fix.  The setting is enforced by iOS, and is not something we can bypass.  If this is something you would like to see changed, you'd need to submit a change request to Apple (and all the other browsers that block location information over http).

     

    All that being said, I don't think we consider this to be broken.  As I mentioned, it's not a good idea to be broadcasting your users location information over an easily intercepted connection.  

     

    Thanks!

     

    Danny
    0
  • Permanently deleted user
    Thank you Daniel for your  kind reply .

     

    Best,

     

    Fatin
    0
  • Permanently deleted user
     

     

    How about Android? I got the error below despite the fact the geolocation is activated at the level of device and browser

     

    _img_ alt="User-added image" src="https://latitudegeo--c.na53.content.force.com/servlet/rtaImage?eid=90760000000GrfM&feoid=Body&refid=0EM60000000UjnR"_/_img_

     

    _img_ alt="User-added image" src="https://latitudegeo--c.na53.content.force.com/servlet/rtaImage?eid=90760000000GrfM&feoid=Body&refid=0EM60000000UjnW" _/_img_

     

    _img_ alt="User-added image" src="https://latitudegeo--c.na53.content.force.com/servlet/rtaImage?eid=90760000000GrfM&feoid=Body&refid=0EM60000000Ujnb" _/_img_
    0
  • Kevin Penner
    Chrome needs HTTPS for geolocation. https://developers.google.com/web/updates/2016/04/geolocation-on-secure-contexts-only

     

     

     
    0
  • Permanently deleted user
    How about firefox and IE? I got the same error.

     

     
    0
  • Permanently deleted user
    Hi Jamal,

     

    Have you uncheck "Never allow websites to request your physical location" in privacy settings of your Internet Options?
    0
  • Permanently deleted user
    Hi Jamal,

     

    As the web continues to develop, more and more browsers will begin requiring SSL when accessing your location.  If you're getting the error in IE and Firefox, please enable SSL and try again.

     

    Thanks,

     

    Danny
    0
  • Permanently deleted user
    H Leo Liu,

     

    Sure. It is activated

     

     

     

    Hi Daniel,

     

    We will be trying to migrate to SSL. However, it is good if we know which operating systems or browsers are still working with geocortex without having geolocation error

     

     
    0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.

Sie haben nicht gefunden, wonach Sie suchten?

Neuer Post