diff options
Diffstat (limited to 'docs/topics/auth')
| -rw-r--r-- | docs/topics/auth/customizing.txt | 2 | ||||
| -rw-r--r-- | docs/topics/auth/default.txt | 4 |
2 files changed, 3 insertions, 3 deletions
diff --git a/docs/topics/auth/customizing.txt b/docs/topics/auth/customizing.txt index 9ae30b4b25..3c73783b24 100644 --- a/docs/topics/auth/customizing.txt +++ b/docs/topics/auth/customizing.txt @@ -64,7 +64,7 @@ That's the basic authentication backend that checks the Django users database and queries the built-in permissions. It does not provide protection against brute force attacks via any rate limiting mechanism. You may either implement your own rate limiting mechanism in a custom auth backend, or use the -mechanisms provided by most Web servers. +mechanisms provided by most web servers. The order of :setting:`AUTHENTICATION_BACKENDS` matters, so if the same username and password is valid in multiple backends, Django will stop diff --git a/docs/topics/auth/default.txt b/docs/topics/auth/default.txt index 82cf58c128..a89949894f 100644 --- a/docs/topics/auth/default.txt +++ b/docs/topics/auth/default.txt @@ -347,7 +347,7 @@ inherit the permissions of the concrete model they subclass:: .. _auth-web-requests: -Authentication in Web requests +Authentication in web requests ============================== Django uses :doc:`sessions </topics/http/sessions>` and middleware to hook the @@ -451,7 +451,7 @@ How to log a user out When you call :func:`~django.contrib.auth.logout()`, the session data for the current request is completely cleaned out. All existing data is - removed. This is to prevent another person from using the same Web browser + removed. This is to prevent another person from using the same web browser to log in and have access to the previous user's session data. If you want to put anything into the session that will be available to the user immediately after logging out, do that *after* calling |