Use Let's Encrypt for HTTPS #31

New Issue

2017-03-13T19:20:45-05:00

mattbk commented

2017-03-13 19:20:45 -05:00

(Migrated from github.com)

Via email:

Nonsecure Collection of Passwords will trigger warnings in Chrome 56 for http://northernplainsathletics.com/

To: owner of http://northernplainsathletics.com/

Beginning in January 2017, Chrome (version 56 and later) will mark pages that collect passwords or credit card details as “Not Secure” unless the pages are served over HTTPS.

The following URLs include input fields for passwords or credit card details that will trigger the new Chrome warning. Review these examples to see where these warnings will appear, and so you can take action to help protect users’ data. The list is not exhaustive.

http://northernplainsathletics.com/user

The new warning is the first stage of a long-term plan to mark all pages served over the non-encrypted HTTP protocol as “Not Secure”.
Here’s how to fix this problem:

Use HTTPS pages to collect sensitive information

To prevent the “Not Secure” notification from appearing when Chrome users visit your site, move collection of password and credit card input fields to pages served using the HTTPS protocol.

Via email: ``` Nonsecure Collection of Passwords will trigger warnings in Chrome 56 for http://northernplainsathletics.com/ To: owner of http://northernplainsathletics.com/ Beginning in January 2017, Chrome (version 56 and later) will mark pages that collect passwords or credit card details as “Not Secure” unless the pages are served over HTTPS. The following URLs include input fields for passwords or credit card details that will trigger the new Chrome warning. Review these examples to see where these warnings will appear, and so you can take action to help protect users’ data. The list is not exhaustive. http://northernplainsathletics.com/user The new warning is the first stage of a long-term plan to mark all pages served over the non-encrypted HTTP protocol as “Not Secure”. Here’s how to fix this problem: Use HTTPS pages to collect sensitive information To prevent the “Not Secure” notification from appearing when Chrome users visit your site, move collection of password and credit card input fields to pages served using the HTTPS protocol. ```

mattbk commented

2019-02-10 13:31:46 -06:00

(Migrated from github.com)

This is handled for free through the host, closing.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: matt/npa#31