Starting from Chromium 50, when trying to use geolocation on HTTP sites, the JS console reports that this feature is blocked:
getCurrentPosition () and watchPosition () no longer work on insecure origins. To use this feature, you should consider connecting your application to a secure origin, such as HTTPS. See https://goo.gl/rStTGz for more details.
What type of certificate will be enough to use this feature?
There are the following types of certificates:
- self-signed
- signed by a not trusted certification center (SC)
- signed by a trusted certification authority
In turn, the latter is divided into:
- Esential SSL
- Instant SSL
- SGC SSL certificate
- Normal Wildcard
- EV (Extended Validation) certificate
- EV Wildcard and EV SGC
as I understand it, the self-signed allows you to encrypt traffic and use the HTTPS protocol, but in no way certifies that the site is in fact a site for which it claims to be
Essential SSL and Instant SSL must already be certified by a certification authority.
In order to use geolocation in chrome, will there be enough a self-signed certificate?
official record from google:
https://developers.google.com/web/updates/2016/04/geolocation-on-secure-contexts-only
