Re:HTTPS on Your Landing Page Is Important
by JohnTHaller on Wednesday December 13, 2017 @11:25PM
(#15919939)
Microsoft's login experience has been generally broken for years. Multiple redirects through different domains. Heck it uses Javascript redirects. In 2017. So your back button won't work. And it has a habit of just not working. I went to visit a public page on docs.microsoft.com and wound up dead on a white page on login.live.com because it decided I needed to be redirected to login. Just to view a docs page.
[ Parent
| on HN ]
Re:HTTPS on Your Landing Page Is Important
by noxToken on Thursday December 14, 2017 @09:45AM
(#15922592)
I don't know if this is still the case, but you couldn't login if you had 3rd party cookies disabled. Somewhere in the authentication phase, it would silently fail. No error message like incorrect username/password. You'd get kicked back to the login screen as if you just got there. It was a hassle trying to find exactly which cookies were necessary.
Re:HTTPS on Your Landing Page Is Important
by drchickensalad on Thursday December 14, 2017 @09:05AM
(#15922308)
What is the alternative to javascript redirecting when you can't do it as the http response?
Re:HTTPS on Your Landing Page Is Important
by JohnTHaller on Thursday December 14, 2017 @12:09PM
(#15924052)
It spits out an HTML page with no body that solely does a Javascript redirect. Put it in the http response.
Re:HTTPS on Your Landing Page Is Important
by heywire on Thursday December 14, 2017 @03:17PM
(#15926542)
It is even worse if you work for a large company with Office 365 that uses your organizations domain for authentication. I think there are about 6 redirects to get logged in. Even worse than that, they made us create a "personal" account with the exact same username for accessing MSDN because it wasn't compatible with our SSO at the time. So every time I log in, I have to type in my username, wait for the redirect, then choose personal account, wait for redirect, etc...