Persistent but inconsistent bouts of this certificates problem. Especially bad with outlook.com / live.com but also dogging yahoo.com. These certificates are often inappr… (閱讀更多)
Persistent but inconsistent bouts of this certificates problem. Especially bad with outlook.com / live.com but also dogging yahoo.com. These certificates are often inappropriate to the domain in question, coming from "sister" domains (like outlook.com login goes to blue.live.com, and so on). But this is not the point. The point is, I want to just kill and be done with certificates. You fix this one release and break it the next. Option to add exceptions goes away, comes back, goes away with no evident reason. MSIE is better behaved, shame on you. Advice to go ask the certificate supplier is pointless, they do not respond. Advice to check antivirus has been done, still ineffective with all Web scanning disabled. Clock is fine. This is simple inability to deal with messy bookkeeping at the destination end. You can't handle it, I get it. But you could at least leave me an "out". Yes, you could.
Just tell me how to eliminate certificates checking (or tell me a browser that does a less crappy job of following these chains and I'll quit using Firefox today). A browser that won't browse your most common email providers is not worth keeping. Does not matter how you think the world should be, if you can't provide connectivity despite sloppy housekeeping at the other end, you can't provide connectivity, which means you are not useful.