generated from nginx/template-repository
-
Notifications
You must be signed in to change notification settings - Fork 121
Labels
🔥 p2Priority 2: Impacts production; non-emergencyPriority 2: Impacts production; non-emergencyproduct/wafIssues related to F5 WAF for NGINXIssues related to F5 WAF for NGINX
Description
Describe the bug you have identified
In https://docs.nginx.com/waf/install/virtual-environment/ between section Update configuration files and Post-installation checks there should be a small section mentioning that NGINX should be restarted in order for the WAF to be started. Post-installation checks assume this has been done while not explicitly mentioned in the docs
Which product or products does this request relate to?
F5 WAF for NGINX
Steps to reproduce the bug
There's a missing step in ttps://docs.nginx.com/waf/install/virtual-environment/
What is the expected or desired behaviour?
The reader should be made aware that NGINX process restart is mandatory and needed
What environments or versions does this bug affect?
N/A
Any additional information
No response
Metadata
Metadata
Assignees
Labels
🔥 p2Priority 2: Impacts production; non-emergencyPriority 2: Impacts production; non-emergencyproduct/wafIssues related to F5 WAF for NGINXIssues related to F5 WAF for NGINX