Origin behind vGuard

If you are reading this, the request passed the firewall and reached the origin.

These should each be blocked with a 403 and appear in the Attack log:

• SQL injection in a query parameter
• Cross-site scripting
• Sensitive file reference
• Path traversal — needs curl --path-as-is, because a browser and curl both resolve ../ before sending it

The dashboard is at panel.waf.1ti.click:9443.