diff options
| author | David Smith <smithdc@gmail.com> | 2021-07-23 07:48:16 +0100 |
|---|---|---|
| committer | Mariusz Felisiak <felisiak.mariusz@gmail.com> | 2021-07-29 06:24:12 +0200 |
| commit | 1024b5e74a7166313ad4e4975a15e90dccd3ec5f (patch) | |
| tree | 05d75177f183de5e3c58dbf25a3f71ff4a5c820a /docs/topics/auth/customizing.txt | |
| parent | acde91745656a852a15db7611c08cabf93bb735b (diff) | |
Fixed 32956 -- Lowercased spelling of "web" and "web framework" where appropriate.
Diffstat (limited to 'docs/topics/auth/customizing.txt')
| -rw-r--r-- | docs/topics/auth/customizing.txt | 2 |
1 files changed, 1 insertions, 1 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 |