Describe the bug
The URL sent in the "[peeringdb.com] Please Confirm Your Email Address" starts http://www.peeringdb.com/accounts/confirm-email/ instead of https://www.peeringdb.com/accounts/confirm-email/
The http:// URL redirects to https:// but it would be nice to put https:// in the offered URL
To Reproduce
Steps to reproduce the behavior:
- Tick to "Require users to periodically re-confirm their email address:" option in the users tab of the organization management control
- Select a period
- Wait for the message
Expected behavior
Put https:// in the offered link
Who is affected by the problem?
Anyone in an organization that requires accounts to reconfirm periodically
What is the impact?
Those who notice might trust the http:// link less, or feel obliged to rewrite it instead of just clicking on it
Are there security concerns?
https:// has been the preferred protocol for some years now
Are there privacy concerns?
No really
What are the proposed actions?
Update the message template to default to https://
What is the proposed priority?
For discussion
Provide a rationale for any/all of the above
Our industry has trained users to avoid trusting http:// URL and we should use https:// whenever possible
Additional context
Add any other context about the problem here.
Describe the bug
The URL sent in the "[peeringdb.com] Please Confirm Your Email Address" starts http://www.peeringdb.com/accounts/confirm-email/ instead of https://www.peeringdb.com/accounts/confirm-email/
The http:// URL redirects to https:// but it would be nice to put https:// in the offered URL
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Put https:// in the offered link
Who is affected by the problem?
Anyone in an organization that requires accounts to reconfirm periodically
What is the impact?
Those who notice might trust the http:// link less, or feel obliged to rewrite it instead of just clicking on it
Are there security concerns?
https:// has been the preferred protocol for some years now
Are there privacy concerns?
No really
What are the proposed actions?
Update the message template to default to https://
What is the proposed priority?
For discussion
Provide a rationale for any/all of the above
Our industry has trained users to avoid trusting http:// URL and we should use https:// whenever possible
Additional context
Add any other context about the problem here.