You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm aware, the practice is that we bump protocol even if the resulting URL gets redirected back to insecure (same for mixed-content and other HTTPS implementation details). The idea is that website owners would eventually fix their site configuration and content to be served in a secure manner.
(having said that, it's probably a good idea to raise such issues with said website owners.)
@srl295: In case you have any influence on that particular redirection, I'd be nice to get it fixed to remain on HTTPS. Or even better: to offer HTTPS over the default domain.
@srl295 Please leave it as-is for now. The SSL domain has been there for many-many years, so it's safe to assume that it's fairly stable. We can update it once it breaks (or any fix is being applied to the website.)
0 commit comments