← Problem Library
Network L4 NETWORK-015 · 21 min

After adding a WAF rule, only certain JSON requests return 403

Reproduces and analyzes a situation where most requests are fine but only a specific payload pattern is caught by the security rule.

NetworkPlatform ReliabilityLevel 4Pro21 min
Scenario

A scenario that narrows down the root cause, centered on adjusting the boundary between the edge security rule and legitimate business requests, in the situation of only certain JSON requests returning 403 after adding a WAF rule.

What to check first
  • Identify the primary failure signal in the Edge Security scenario.
  • Separate visible symptoms from the underlying technical dependency.
  • Describe the safest recovery path and the follow-up prevention work.
Checking checklist
  1. Summarize the current impact and the last known change.
  2. Collect direct evidence from logs, runtime state, and configuration before changing anything.
  3. Separate immediate recovery from permanent prevention work.
Recovery and prevention

Choose the smallest safe recovery action first, then record the prevention work that reduces repeat incidents.

Questions worth viewing together
Should I translate commands, logs, or product names?

No. Keep commands, logs, file names, APIs, and product names unchanged, then explain the reasoning in the selected UI language.

What should the answer focus on?

State the root cause, the evidence that supports it, and the safest recovery direction.

Why can the scenario remain in the original language?

The source scenario is treated as an incident artifact. Guidance, checklist, hints, and explanations can be localized around it.