Insecure connection password warning in Firefox
Revision Information
- Revision id: 226761
- Created:
- Creator: emsin
- Comment: Changed wording in a few sentences, also added a clarification of "HTTPS" vs "HTTP", and reworded the introduction to increase flow.
- Reviewed: No
- Ready for localization: No
Revision Source
Revision Content
When a login page you’re viewing does not have a secure connection, Firefox will display a lock icon with a red strike-through in the address bar.
If you enter personal information, such as a password or credit card number, on such insecure pages, digital easedroopers may be able to access it.
You will also see a warning message when you click inside the login box to enter a username or password.
Note: When you start entering your login information, the warning message can obscure the password entry box. To dismiss the warning, either press the Tab key or click on the page background after you type in your username.
What can I do if a login page is insecure?
If the login page is insecure, check if a secure version exists by adding https:// in front of the website address. You can also contact the website administrator and ask them to secure the connection.
- The image "https_secure_lock_gree n_icon" does not exist.
About insecure pages
Pages that transmit private information, such as credit cards numbers, personal information, and passwords, need to have a secure connection to help prevent attackers from stealing your information. (Tip: A secure connection will have "HTTPS" in the address bar, along with a green lock icon"HTTPS" in the address bar, along with a gray lock icon.)
Pages that don’t transmit any private information can use an unencrypted connection (HTTP instead of HTTPS). It is advised to not enter private information, such as passwords, on these websites, as your information can be stolen through an insecure connection.
Note for developers
For developers looking to learn more about this warning, please see this page. The page explains when and why Firefox shows this warning, and will also provide some details on how to fix the issue. For more information, see this blog post and this Site Compatibility document.