Skip to content

Commit 76e6c51

Browse files
committed
Add glossary entry
1 parent 4eebc47 commit 76e6c51

File tree

2 files changed

+15
-11
lines changed

2 files changed

+15
-11
lines changed

src/content/docs/waf/rate-limiting-rules/request-rate.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -9,16 +9,16 @@ head:
99
content: How Cloudflare determines the request rate
1010
---
1111

12-
import { Example } from "~/components";
12+
import { Example, GlossaryTooltip } from "~/components";
1313

14-
Cloudflare keeps separate rate counters for rate limiting rules for each value combination of the rule characteristics.
14+
Cloudflare keeps separate rate counters for rate limiting rules for each value combination of the <GlossaryTooltip term="rule characteristics">rule characteristics</GlossaryTooltip>.
1515

1616
Consider a rule configured with the following characteristics:
1717

1818
- IP address
1919
- HTTP header `x-api-key`
2020

21-
In this case, two incoming requests with the **same** value for the HTTP header `X-API-Key` with **different** IP addresses are counted separately, since the value combination is different. Additionally, counters are not shared across data centers.
21+
In this case, two incoming requests with the same value for the HTTP header `X-API-Key` but with different IP addresses are counted separately, since the value combination is different. Additionally, counters are not shared across data centers.
2222

2323
The counting model of this rate limiting rule is based on the number of incoming requests. Enterprise customers with Advanced Rate Limiting can also configure rules whose counting model is based on the complexity of serving incoming requests. Refer to [Complexity-based rate limiting](#complexity-based-rate-limiting) for more information.
2424

src/content/glossary/waf.yaml

Lines changed: 12 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -35,6 +35,10 @@ entries:
3535
associated_products:
3636
- Magic Firewall
3737

38+
- term: LLM
39+
general_definition: |-
40+
a machine learning model that can comprehend and generate human language text. It works by analyzing massive data sets of language.
41+
3842
- term: mitigated request
3943
general_definition: |-
4044
a request to which Cloudflare applied a terminating action such as block or challenge.
@@ -43,10 +47,18 @@ entries:
4347
general_definition: |-
4448
classifies rules of the OWASP managed ruleset according to their aggressiveness.
4549
50+
- term: prompt injection
51+
general_definition: |-
52+
the process of overwriting the system prompt for a large language model (LLM), which instructs the LLM on how to respond to user input.
53+
4654
- term: rate limiting
4755
general_definition: |-
4856
rate limiting is a technique used in computer systems to control the rate at which requests are processed. It can be used as a security measure to prevent attacks, or to limit resource usage in your origin servers.
4957
58+
- term: rule characteristics
59+
general_definition: |-
60+
The set of parameters of a rate limiting rule that define how Cloudflare tracks the rate for the rule.
61+
5062
- term: SIEM
5163
general_definition: |-
5264
a Security Information and Event Management (SIEM) solution collects, analyzes, and correlates data to help manage security incidents, detect anomalies, and meet compliance requirements.
@@ -57,11 +69,3 @@ entries:
5769
- term: threat score
5870
general_definition: |-
5971
the threat score was a score from `0` (zero risk) to `100` (high risk) classifying the IP reputation of a visitor. Currently, the threat score is always `0` (zero).
60-
61-
- term: LLM
62-
general_definition: |-
63-
a machine learning model that can comprehend and generate human language text. It works by analyzing massive data sets of language.
64-
65-
- term: prompt injection
66-
general_definition: |-
67-
the process of overwriting the system prompt for a large language model (LLM), which instructs the LLM on how to respond to user input.

0 commit comments

Comments
 (0)