Skip to content

... content and ... content detect malformed content #1216

@osokin

Description

@osokin

Describe the bug

Two contents detect another content.

To reproduce

Steps to reproduce the behavior:

  1. Open https://docs.nginx.com/waf/fundamentals/technical-specifications/#supported-security-policy-features
  2. View output
  3. See unclear text message in the Description field: XML content and JSON content detect malformed content and detects signatures in the element values. Default policy checks maximum structure depth. It is possible to enable more size restrictions: maximum total length of XML/JSON data, maximum number of elements are more.

Expected behavior

The phrase needs to be improved. It's, probably, speaking about a content profile there, isn't it?

Your environment

macOS/Chrome

Additional context

No any other context about the problem here.

Sensitive Information

No any sensitive information such as authentication credentials or license keys.

Metadata

Metadata

Assignees

Labels

⚠️ p3Priority 3: Does not impact production environment or is a nice-to-havebugSomething isn't workingproduct/wafIssues related to F5 WAF for NGINX

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions