diff options
| author | Alex Gaynor <alex.gaynor@gmail.com> | 2015-12-19 23:55:15 -0500 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2015-12-21 06:47:11 -0500 |
| commit | d7580e286ac9c48e410d59281720205d6f5dda10 (patch) | |
| tree | 38a635c9b42a18727ef027f205f3621537f648bd /docs/topics/security.txt | |
| parent | fa9ce4e9a691e4f8c8b093784bac752e488dc60b (diff) | |
Removed a misleading comment about HTTPS.
For all practical purposes, there are no common cases for which a
website cannot be deployed with HTTPS.
Diffstat (limited to 'docs/topics/security.txt')
| -rw-r--r-- | docs/topics/security.txt | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/docs/topics/security.txt b/docs/topics/security.txt index 1f2f0f199e..221036e328 100644 --- a/docs/topics/security.txt +++ b/docs/topics/security.txt @@ -120,11 +120,11 @@ for a small section of the site. SSL/HTTPS ========= -It is always better for security, though not always practical in all cases, to -deploy your site behind HTTPS. Without this, it is possible for malicious -network users to sniff authentication credentials or any other information -transferred between client and server, and in some cases -- **active** network -attackers -- to alter data that is sent in either direction. +It is always better for security to deploy your site behind HTTPS. Without +this, it is possible for malicious network users to sniff authentication +credentials or any other information transferred between client and server, and +in some cases -- **active** network attackers -- to alter data that is sent in +either direction. If you want the protection that HTTPS provides, and have enabled it on your server, there are some additional steps you may need: |