Firewall rule matching on path with query string — expected behaviour?

Question

A custom rule "path equals /api/login" does not match /api/login?next=/. Is the path compared with or without the query?

Priya Raman · Answer

Without the query — but "equals" compares the full path, and the rule engine normalises trailing slashes. Can you check whether the request is actually /api/login/?

Firewall rule matching on path with query string — expected behaviour?

Related topics

Suggested topics