[Bug]: Wrong NGINX configuration files for NGINX + WAF on VM/bare metal

[fabriziofiorucci]

Describe the bug you have identified

Here https://docs.nginx.com/waf/install/virtual-environment/#update-configuration-files the docs mention that:

The Enforcer address must be added at the http context:

app_protect_enforcer_address 127.0.0.1:50000;

This is clearly wrong as the bare metal/VM version of the WAF (former NAPv4) doesn't rely on containers and shouldn't use app_protect_enforcer_address. I tried to create a pull request but that section is included by several pages:

• https://docs.nginx.com/waf/install/docker/#update-configuration-files
• https://docs.nginx.com/waf/install/kubernetes/#use-manifests-to-install-f5-waf-for-nginx
• https://docs.nginx.com/waf/install/virtual-environment/#update-configuration-files

it should probably be split as the virtual-environment case differs from docker and kubernetes

Which product or products does this request relate to?

F5 WAF for NGINX

Steps to reproduce the bug

Browse to https://docs.nginx.com/waf/install/virtual-environment/#update-configuration-files

What is the expected or desired behaviour?

The correct configuration steps should be displayed for bare metal/VM

What environments or versions does this bug affect?

Docs-related, bug in the bare metal/VM part

Any additional information

No response