Julie on 22 Apr, 2021 03:05 PM
Lots of questions here -
Refresh, yes. Occurred over several days with complete reboot on 2 machines...desktop, and Surface Pro. 1st happened with new UI.
Cleared cache on desktop, disabled plugins, and note difference window display on 2 different browsers. Edge & Brave browsers work fine.
The Surface Pro never in it’s history had tried to access Caltopo, since I use desktop only for backup of financial proggies. So that was a virgin login attempt for the Surface Pro. Surface Pro Chrome/Firefox displays the same image as the desktop Chrome/Firefox.
Ben Lantow on 23 Apr, 2021 03:47 AM
Took a look at these logs with one of our engineers, the security settings you have set on those browsers is such that its not allowing the Caltopo application to run. Compared to the "typical" browser settings, these security settings are much more locked down. We will look into the issues they are flagging based on those logs but cannot promise a quick fix. I'm glad for the moment being you have a functional work around, but we'll work on figuring out what we can do to get this working in your specific use case.
I am running latest version, 88.0. What I found was that the security mode was set to “Enable HTTPS-Only, in all windows”. I don’t recall overtly setting this level. What I am suggesting is that like Chrome, the rollout of v88.0 defaulted to HTTPS-Only.
So Firefox works now, and Chrome I still need to find the setting.
Perhaps Caltopo can use HTTPS for their opening page, before login, to preclude these issues in the future?
Julie closed this discussion
on 23 Apr, 2021 08:45 PM.
Ben Lantow re-opened this discussion
on 23 Apr, 2021 09:46 PM
Ben Lantow on 23 Apr, 2021 09:46 PM
I've looked into this more, including testing on my macbook with chrome 90 and I'm still unable to duplicate this issue even using incognito and dumping my entire cache and cookie history. There must be some sort of security settings you opted to set on your machine specifically. With regard to your comment, the changes in chrome are to load a site using HTTPS by default. We've had a HTTPS redirect in place for quite some time so users have been getting a secure connection. (try typing in http://caltopo.com it will redirect to HTTPS).
We'll dig into those logs in the future, but as far as we are able to tell so far this appears to be an isolated issue.