Skip to content

Commit 75f1998

Browse files
authored
Update throttling docs (#8424)
1 parent 0b88583 commit 75f1998

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

docs/api-guide/throttling.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,9 @@ Multiple throttles can also be used if you want to impose both burst throttling
1919

2020
Throttles do not necessarily only refer to rate-limiting requests. For example a storage service might also need to throttle against bandwidth, and a paid data service might want to throttle against a certain number of a records being accessed.
2121

22-
**The application-level throttling that REST framework provides should not be considered a security measure or protection against brute forcing or denial-of-service attacks. Deliberately malicious actors will always be able to spoof IP origins, and application-level throttling is intended for implementing policies such as different business tiers and basic protections against service over-use.**
22+
**The application-level throttling that REST framework provides should not be considered a security measure or protection against brute forcing or denial-of-service attacks. Deliberately malicious actors will always be able to spoof IP origins. In addition to this, the built-in throttling implementations are implemented using Django's cache framework, and use non-atomic operations to determine the request rate, which may sometimes result in some fuzziness.
23+
24+
The application-level throttling provided by REST framework is intended for implementing policies such as different business tiers and basic protections against service over-use.**
2325

2426
## How throttling is determined
2527

0 commit comments

Comments
 (0)