> The SSL error happens because the server sends a certificate which is only valid for the www subdomain.
This happens more and more to me, even now with two of my banks' websites.
Did anything change recently in the standard / browser-enforcement of the standard that'd make that more common?
Or in the way some CA emits these?
I'm really noticing that more and more.
It's also not clear why many people have no issue and are hence posting links that work for some and not for others: is a major browser fine with these while another would be stricter?
Not necessarily this specific manifestation... but something still worth considering.
Large enough businesses tend to clam up for changes in certain quarters. This makes hot spots for renewals/expiration or really anything potentially risky.
Nobody wants to do twice the paperwork for maintenance when it lands in sales-season 'change freezes'. I actually burned half a year of lifetime once just to get a more favorable schedule
This happens more and more to me, even now with two of my banks' websites.
Did anything change recently in the standard / browser-enforcement of the standard that'd make that more common?
Or in the way some CA emits these?
I'm really noticing that more and more.
It's also not clear why many people have no issue and are hence posting links that work for some and not for others: is a major browser fine with these while another would be stricter?