[OPLINTECH] HTML5 geolocation functions over http in Chrome

[Karl Jendretzky]

All,

Chrome pausing auto-playing flash content starting today was news worthy,
but it looks like that's not all that's changed. As of this morning when
you try and use the Geolocation functions of HTML5 over a non-https
connection, Chrome throws a warning in the background...

"getCurrentPosition() and watchPosition() are deprecated on insecure
origins, and support will be removed in the future. You should consider
switching your application to a secure origin, such as HTTPS. See
https://goo.gl/rStTGz for more details."

Though it's only a warning, it seems to stop the execution of the script. I
think this is a bug, and will likely be fixed rather quickly by Google. In
the meantime if you have something that uses those functions and people are
reporting issues, that's likely the reason.

For OPLIN the only real problem it causes is for remote patrons
authenticating to statewide databases. Until I force that landing page to
use https, they'll have to enter a library card.

Karl Jendretzky
IT Manager - Ohio Public Library Information Network
(614) 728-1515karl at oplin.ohio.gov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.oplin.org/pipermail/oplintech/attachments/20150901/f3a9257a/attachment.html>