How to know when firefox's "potential security risk ahead" is a false alarm?
by linuxuser371038 from LinuxQuestions.org on (#6Q763)
I have been doing a lot of cycling research lately and a specific well regarded website keeps popping up in results however some of its pages display that warning while others don't.
So in cases where I would like to view the information within, and the warning arises, how do you ascertain if that warning is a false alarm?
Look at the example:
This one produces the warning:
https://sheldonbrown.com/speeds.html
While this page, on the same site, doesn't:
https://www.sheldonbrown.com/frames.html
What causes this to happen and how does one figure out if it is erroneous?
Ok I just clicked the first link and it didn't produce the warning. I looked the exact url and it seems when navigated through search engine it does no www while when I clicked the link on this post is did produce www.
So not sure why one triggers the warning and the other doesn't. Going from my hazy memory of once setting ssl for a domain I seem to remember you should do wildcard to account for www and other url extensions like that so it that the problem here, that the ssl certificate has not been issued for the none www?
Regardless of that, that might not be the issue in other cases, on other sites when the warning arises so how to figure out if they are ok in wider cases?
So in cases where I would like to view the information within, and the warning arises, how do you ascertain if that warning is a false alarm?
Look at the example:
This one produces the warning:
https://sheldonbrown.com/speeds.html
While this page, on the same site, doesn't:
https://www.sheldonbrown.com/frames.html
What causes this to happen and how does one figure out if it is erroneous?
Ok I just clicked the first link and it didn't produce the warning. I looked the exact url and it seems when navigated through search engine it does no www while when I clicked the link on this post is did produce www.
So not sure why one triggers the warning and the other doesn't. Going from my hazy memory of once setting ssl for a domain I seem to remember you should do wildcard to account for www and other url extensions like that so it that the problem here, that the ssl certificate has not been issued for the none www?
Regardless of that, that might not be the issue in other cases, on other sites when the warning arises so how to figure out if they are ok in wider cases?