Skip to content

Commit 7ca4284

Browse files
committed
acrolinx tweaks
1 parent 4c07876 commit 7ca4284

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/web-application-firewall/afds/captcha-challenge.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ ms.date: 04/29/2025
1616
1717
Azure Web Application Firewall (WAF) offers a CAPTCHA feature designed to differentiate human users from automated bots. This interactive challenge requires suspected traffic to complete a CAPTCHA test, blocking malicious automated requests while allowing legitimate users to proceed seamlessly. As a result, WAF helps protect applications from bot-driven attacks, including brute-force attempts and account takeover risks.
1818

19-
CAPTCHA on Azure WAF is particularly useful in login and sign-up flows where human authentication is crucial to protect sensitive user data. It acts as a strong defense against a variety of automated threats, preventing bots from accessing critical website elements like login pages and forms, and reducing spam by ensuring only real users can submit comments, register accounts, or complete transactions.
19+
CAPTCHA on Azure WAF is useful in login and sign-up flows where human authentication is crucial to protect sensitive user data. It acts as a strong defense against various automated threats, preventing bots from accessing critical website elements like login pages and forms, and reducing spam by ensuring only real users can submit comments, register accounts, or complete transactions.
2020

2121
Incorporating CAPTCHA into Azure WAF not only enhances security but also minimizes friction for legitimate users. This balance strengthens the overall protection of web applications against sophisticated automated threats.
2222

@@ -29,7 +29,7 @@ When the CAPTCHA challenge is active on Azure WAF, any client's HTTP(s) request
2929

3030
## Expiration
3131

32-
The WAF **Policy settings** define the CAPTCHA challenge cookie validity lifetime in minutes, determining how long a user remains validated before facing a new challenge. Once the lifetime expires, the user must complete the CAPTCHA challenge again to verify their identity. The lifetime is configurable between 5 and 1,440 minutes, with a default setting of 30 minutes. The CAPTCHA challenge cookie name is `afd_azwaf_captcha` on Azure Front Door.
32+
The WAF **Policy settings** define the CAPTCHA challenge cookie validity lifetime in minutes, determining how long a user remains validated before facing a new challenge. Once the lifetime expires, the user must complete the CAPTCHA challenge again to verify their identity. The lifetime is configurable between 5 and 1,440 minutes, with a default setting of 30 minutes. The CAPTCHA challenge cookie name is `afd_azwaf_captcha` on Azure Front Door.
3333

3434
> [!NOTE]
3535
> The CAPTCHA challenge expiration cookie is injected into the user’s browser after successfully completing the challenge.
@@ -42,7 +42,7 @@ The WAF **Policy settings** define the CAPTCHA challenge cookie validity lifetim
4242

4343
- **POST body size restriction**: The first request that triggers a CAPTCHA challenge will be blocked if its POST body exceeds 128 KB.
4444

45-
- **Non-HTML embedded resources**: CAPTCHA is specifically designed for HTML resources. Placing CAPTCHA in front of non-HTML resources, such as images, CSS, or JavaScript files, may likely result in issues with content loading and rendering.
45+
- **Non-HTML embedded resources**: CAPTCHA is designed for HTML resources. Placing CAPTCHA in front of non-HTML resources, such as images, CSS, or JavaScript files, may likely result in issues with content loading and rendering.
4646

4747
- **Browser compatibility**: CAPTCHA isn't supported on Microsoft Internet Explorer. It's compatible with the latest versions of Microsoft Edge, Chrome, Firefox, and Safari.
4848

0 commit comments

Comments
 (0)