Bad certificate error caused by missing www in URL
When clicking on a link that does not include "www." in the URL, I am presented with an error SSL_ERROR_BAD_CERT_DOMAIN. But the certificate is good. the problem was the URL that did not include the "www."
This would be an easy fix! Just add "www." to the URL if it is missing. It could eliminate user confusion if they do not understand.
Just a suggestion
Chosen solution
Hi, some sites don't use www so I'm not sure it would be a good idea to make this universal. But maybe there should be a "try it this way" link on the error page to help users know what to try next?
Mozilla launched an "Ideas" site where you could submit your suggestion: https://connect.mozilla.org/
Meanwhile, if the problem is on a site you visit often or care about for other reasons, please let them know. Before HTTPS was in such wide use, it was okay to redirect from the base domain to the www subdomain using HTTP, but with browsers trying HTTPS first or users opting into HTTPS only, sites should upgrade their certificates to cover the redirect as well.
Read this answer in context 👍 0All Replies (1)
Chosen Solution
Hi, some sites don't use www so I'm not sure it would be a good idea to make this universal. But maybe there should be a "try it this way" link on the error page to help users know what to try next?
Mozilla launched an "Ideas" site where you could submit your suggestion: https://connect.mozilla.org/
Meanwhile, if the problem is on a site you visit often or care about for other reasons, please let them know. Before HTTPS was in such wide use, it was okay to redirect from the base domain to the www subdomain using HTTP, but with browsers trying HTTPS first or users opting into HTTPS only, sites should upgrade their certificates to cover the redirect as well.