diff options
| author | Tim Graham <timograham@gmail.com> | 2013-11-18 19:10:58 -0500 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2013-11-18 19:11:33 -0500 |
| commit | 44469af34b98df85806cb9ad305b0504f3e22df7 (patch) | |
| tree | e3ad00411e57c11fd756a475687d48b994acabd0 | |
| parent | 833f7d11e8f1d0171bac23e2e78c1111a83fbeaa (diff) | |
[1.6.x] Fixed typo in topics/http/sessions.txt.
Backport of 9348fc5628 from master
| -rw-r--r-- | docs/topics/http/sessions.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/topics/http/sessions.txt b/docs/topics/http/sessions.txt index 8adaa14c39..d8aa2d5ccc 100644 --- a/docs/topics/http/sessions.txt +++ b/docs/topics/http/sessions.txt @@ -659,7 +659,7 @@ controlled by trusted users (or, are at least unable to set cookies). For example, an attacker could log into ``good.example.com`` and get a valid session for his account. If the attacker has control over ``bad.example.com``, he can use it to send his session key to you since a subdomain is permitted -to set cookies on `*.example.com``. When you visit ``good.example.com``, +to set cookies on ``*.example.com``. When you visit ``good.example.com``, you'll be logged in as the attacker and might inadvertently enter your sensitive personal data (e.g. credit card info) into the attackers account. |
