[OPLINTECH] HTML5 geolocation functions over http in Chrome

[Karl Jendretzky]

Hah, looks like it being broken wasn't directly linked to https.

Google's own examples are broken in Chrome.

https://developers.google.com/maps/documentation/javascript/examples/map-geolocation

Oh well, oplin.org has https now.

Karl Jendretzky
IT Manager - Ohio Public Library Information Network
(614) 728-1515karl at oplin.ohio.gov


On Tue, Sep 1, 2015 at 10:37 AM, Chad Neeper <cneeper at level9networks.com>
wrote:

> Thanks for the heads-up, Karl.
>
> Worth noting is that this is likely just the beginning of a whole slew of
> issues over the next several years as browser makers (with Google/Chromium
> currently at the vanguard) make changes that encourage reluctant web devs
> to secure their websites.
>
> We may hear a lot of complaints from patrons and staff, but it's
> ultimately all for a good cause. Of course, our staff and directors don't
> want to hear that...they just want that darned website they're using to
> work correctly. So hang on and enjoy the ride... LOL!
>
>
>
> ______________________________
> *Chad Neeper*
> Senior Systems Engineer
>
> *Level 9 Networks*
> 740-548-8070 (voice)
> 866-214-6607 (fax)
>
> *Full IT/Computer consulting services -- Specialized in libraries and
> schools*
>
> On Tue, Sep 1, 2015 at 10:20 AM, Karl Jendretzky <karl at oplin.ohio.gov>
> wrote:
>
>> 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
>>
>>
>> _______________________________________________
>> OPLINTECH mailing list
>> OPLINTECH at lists.oplin.org
>> http://lists.oplin.org/mailman/listinfo/oplintech
>>
>>
>>
>
> _______________________________________________
> OPLINTECH mailing list
> OPLINTECH at lists.oplin.org
> http://lists.oplin.org/mailman/listinfo/oplintech
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.oplin.org/pipermail/oplintech/attachments/20150901/b51fd0b8/attachment.html>