Skip to content

Commit d2ea6dc

Browse files
authored
Revise best practices for F5 DoS configuration
Updated section headings and added details for F5 DoS configuration in NGINX.
1 parent e4bd803 commit d2ea6dc

File tree

1 file changed

+6
-4
lines changed

1 file changed

+6
-4
lines changed

content/nap-dos/deployment-guide/best-practices.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -10,20 +10,22 @@ type:
1010

1111
This guide shows how to modify your NGINX configuration to enable F5 DoS for NGINX (NGINX App Protect DoS). We will configure NAPDOS to protect a proxy server.
1212

13-
## Load the F5 DoS for NGINX module
13+
## F5 DoS configuration
14+
15+
### Load the F5 DoS for NGINX module
1416

1517
```nginx
1618
load_module modules/ngx_http_app_protect_dos_module.so;
1719
```
1820

19-
## Enable F5 DoS for NGINX
21+
### Enable F5 DoS for NGINX
2022
Add the directive in the appropriate context, You can set it in location, server, or http blocks:
2123

2224
```nginx
2325
app_protect_dos_enable on;
2426
```
2527

26-
## Set a Protected Object name
28+
#### Set a Protected Object name
2729
Choose a unique name. You can set it in location, server, or http blocks.
2830

2931
```nginx
@@ -50,7 +52,7 @@ Capacity limits
5052
- Up to 1,000 Protected Objects in versions 4.4 and later <br>
5153

5254

53-
## Set a Monitor directive
55+
### Set a Monitor directive
5456
The `app_protect_dos_monitor` directive monitors the stress level of a Protected Object by generating requests from localhost (127.0.0.1) that traverse your NGINX configuration like normal client traffic (through the same `server` / `location` / `proxy_pass` chain).
5557
**This directive is mandatory for optimal accuracy (it may be omitted only when using HTTP/1.1, though it is still strongly recommended).**
5658
```nginx

0 commit comments

Comments
 (0)