diff options
| author | Baptiste Mispelon <bmispelon@gmail.com> | 2013-10-02 16:41:04 +0200 |
|---|---|---|
| committer | Baptiste Mispelon <bmispelon@gmail.com> | 2013-10-02 16:41:04 +0200 |
| commit | e1b77238171cc96f4451a06fb4682e2378896238 (patch) | |
| tree | cc23abefd6af2124b835a0f2f3f657224162c5c9 /docs/topics/http | |
| parent | 00a0d3de0204f73d3f05ae99548b1e317bfe336b (diff) | |
Changed the doc to use gender-neutral pronouns when possible.
Diffstat (limited to 'docs/topics/http')
| -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 b336bf4669..c514978f57 100644 --- a/docs/topics/http/sessions.txt +++ b/docs/topics/http/sessions.txt @@ -166,7 +166,7 @@ and the :setting:`SECRET_KEY` setting. cookie backend might open you up to `replay attacks`_. Unlike other session backends which keep a server-side record of each session and invalidate it when a user logs out, cookie-based sessions are not invalidated when a user - logs out. Thus if an attacker steals a user's cookie, he can use that + logs out. Thus if an attacker steals a user's cookie, he or she can use that cookie to login as that user even if the user logs out. Cookies will only be detected as 'stale' if they are older than your :setting:`SESSION_COOKIE_AGE`. |