+Kirkgirls 0 Posted Wednesday at 07:21 AM When looking at a cache page, the browser title bar says "Not secure". Speaking as a user, this certainly doesn't inspire confidence Platform: Windows 10, Edge browser To repro, go to Lists and choose a list Right-click on a list item and open a cache page in a new tab Result: browser title bar says "Not secure" (see attached screen clip) Quote Share this post Link to post
+MartyBartfast 791 Posted Wednesday at 08:33 AM (edited) FWIW this is not a general issue with geocaching.com, but that specific cache page is reporting that it contains potentially unsecure content, perhaps it's the link to Geocheck.org, or something else. E.G. https://coord.info/GC3Q91P reports as not secure but https://coord.info/GC8R279 is OK. Edited Wednesday at 08:44 AM by MartyBartfast Quote Share this post Link to post
+MartyBartfast 791 Posted Wednesday at 08:46 AM Just checked one of my own cache pages which also has a geochecker and that's OK, so perhaps there's some other content on that one cache page. Quote Share this post Link to post
+sernikk 138 Posted Wednesday at 11:41 AM My firefox, told me on GC3Q91P, that: In translation: "Some elements of this site (e.g. images) were not sent in a secure way." But I checked this on Chrome and this cache website was secure, all normal. Maybe it's some kind of a bug regarding different browsers? Quote Share this post Link to post
+capoaira 77 Posted Wednesday at 02:07 PM 2 hours ago, sernikk said: Some elements of this site (e.g. images) were not sent in a secure way. The Geochecker is loaded with http instead of https Quote Share this post Link to post
+cerberus1 3313 Posted Wednesday at 06:12 PM (edited) We've noticed this in some sections of the Help Center too. Thought it might be a Windows 10/edge thing. Edited Wednesday at 06:12 PM by cerberus1 Quote Share this post Link to post
+barefootjeff 3827 Posted Wednesday at 08:38 PM Some of it seems to be related to advertising content on the page which comes and goes with every reload. Quote Share this post Link to post
+thebruce0 2480 Posted Wednesday at 10:06 PM (edited) Check the description source and see if there are any images loaded (or being requested) with an http:// url, rather than https:// That can cause the notice. Edited Wednesday at 10:06 PM by thebruce0 Quote Share this post Link to post