That actually sounds like a constant that determines if HTTP requests get bumped up to HTTPS. So I googled it and discovered that this is pretty much what it does. For a login request, you would expect that this should be enabled, otherwise you are sending passwords in the clear. You probably know all that, but never assume is the IT Tech's motto.
Just tell the client that someone at the server site was working with security certificates and be done with it. Bob S > On Feb 21, 2017, at 18:30 , Phil Davis via use-livecode > <use-livecode@lists.runrev.com> wrote: > > WHAT JUST HAPPENED? The desktop app I mentioned earlier is now (around 6:15 > PM Pacific time) suddenly no longer blowing up during login, and its normal > speed has been restored. I suspect someone at Command Central changed a > server setting... but I see my 'HTTP_UPGRADE_INSECURE_REQUESTS' is still > turned on. > > Whatever magical thing happened, I'm very grateful. But I sure would like to > know what it was so I can tell my client. > > Thanks - > Phil _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
