Insecure connection password warning in Firefox
Revision Information
- Revision id: 190268
- Created:
- Creator: Marcelo Ghelman
- Comment: The Enter/Return key submits the form before typing the password
- Reviewed: Yes
- Reviewed:
- Reviewed by: AliceWyman
- Is approved? Yes
- Is current revision? No
- Ready for localization: Yes
- Readied for localization:
- Readied for localization by: AliceWyman
Revision Source
Revision Content
Firefox will display a lock icon with red strike-through in the address bar, when a login page you’re viewing does not have a secure connection. If you enter a password on such pages, it could be stolen by eavesdroppers and attackers.
You will also see a warning message when you click inside the login box to enter a username or password.
Note: When you start typing in your login information, the warning message can obscure the password entry box. You can press the Tab key after you type in your username (or click on the page background) to dismiss the warning.
What can I do if a login page is insecure?
If a login page is insecure, you can try and see if a secure version of the page exists by typing https:// in front of the website address. You can also try to contact the web administrator for the site and ask them to secure their connection.
About insecure pages
Pages that need to transmit private information, such as credit cards, 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 have an unencrypted connection (HTTP). But, it is advised not to enter private information, such as passwords. The information you enter can be stolen over this 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.