Skip to content

[Request]: Clarify NGINX configuration limitations for F5 WAF for NGINX #1436

@ADubhlaoich

Description

@ADubhlaoich

What would you like the documentation team to work on?

The Configure NGINX features with F5 WAF for NGINX page has a brief note about subrequest limitations.

Certain features do not work well with NGINX, such as modules requiring subrequest when calling or being called from a scope that contains app_protect_enable on.

There should be additional detail added to this:

  • WAF cannot be enabled under location blocks with modules that require subrequest calls
  • If it is enabled, WAF will secure and inspect client-facing requests, but will not inspect internal sub-requests triggered by these modules

Which product or products does this request relate to?

F5 WAF for NGINX

Who is the person directly responsible for initiating this request?

@ohad-perets

Is this request part of a larger initiative or project?

No

Are there important constraints for this request?

No

Does this request have a due date?

November 18th

Any additional information

This information can likely be made more prominent with the use of a call-out shortcode.

Metadata

Metadata

Assignees

Labels

P3 - Normal (TTR: 1 month)Request to address missing, unclear, or inaccurate content. Doesn't block tasks or cause complaints.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions