Operators searching for how to build allow and deny rules for one application usually expect a signature file or a per-site rule editor. The SafeLine pages used here do not publish that syntax, an import format, or a click-path for custom allow and deny entries. They do publish a reverse-proxy model, the fields that define one application, named controls that include a Web Access Control List, and the screens that prove an attack was denied. This is a decision checklist plus one misconfiguration, not an unsupported rule integration.
SafeLine is a self-hosted web application firewall. Deployed in front of an application, it is a reverse proxy: clients pass through it before they reach the server. It filters and monitors HTTP and HTTPS traffic, blocks traffic its policies treat as malicious, and is designed to prevent unauthorized data from leaving the app. Core capabilities named in the introduction include defenses for web attacks, proactive bot abused defense, HTML and JavaScript code encryption, IP-based rate limiting, and a Web Access Control List (https://docs.waf.chaitin.com/en/home). Use those names as planning categories. Do not turn a name into a rule line that no supplied page documents.
One application is one entry in the Web Admin Console. Open Applications and click Add Application. Enter Domain, Port, and Upstream. Domain is the original application domain, hostname, or IP address. Port is the port SafeLine will listen on, such as 80 or 443, and HTTPS applications need the SSL option checked. Upstream is the real address of the original application, and SafeLine forwards traffic to that address. After those fields are set, resolve the domain to the IP address of the server where SafeLine runs (https://docs.waf.chaitin.com/en/GetStarted/AddApplication). That resolution step is part of the rule scope. Traffic that never arrives at SafeLine is outside every allow and deny decision you think you configured.
Build the allow and deny plan as outcomes, then test those outcomes:
- Allow means a request that is not treated as an attack is forwarded to the Upstream address, and the client receives the original application.
- Deny means malicious HTTP or HTTPS traffic is filtered and blocked. The introduction lists SQL injection, XSS, code injection, OS command injection, CRLF injection, LDAP injection, XPath injection, RCE, XXE, SSRF, path traversal, backdoor, brute force, HTTP flood, and bot abused among the attack types the product is meant to address (https://docs.waf.chaitin.com/en/home).
- Rate limiting is a separate throttle for traffic that exceeds defined limits, including DoS attacks, brute-force attempts, and traffic surges. CAPTCHA challenge, authentication challenge, and dynamic protection are also named features. These pages describe what they do, not the per-application form fields, so this checklist does not invent limits, passwords, or encryption settings (https://docs.waf.chaitin.com/en/home).
- A Web Access Control List is listed, which is the closest documented name to allow and deny rules. Because no sample list, IP syntax, or save button is shown here, do not ship a guessed list. Decide the intended allow and deny outcomes, then configure them only on a screen the official docs actually describe.
The concrete misconfiguration is a bypassed listener that looks like a deny-rule miss. You add the application, leave the public DNS record pointed at the origin, and request a documented SQL injection test on your own domain: a query string of id=1+and+1=2+union+select+1. The origin returns its normal page or its own error. The SafeLine attack list stays unchanged. The tempting conclusion is that the deny rule failed to match the payload. The request never entered the reverse proxy, so SafeLine had no chance to allow or deny it. The same bypass also hides allow-path failures, because a direct origin response tells you nothing about Upstream forwarding.
Fix the two fields that define this one application before you edit any broader policy. Point the domain at the SafeLine server IP, as the add-application guide requires. Set Upstream to the real origin address, not to the public name if that name now resolves to SafeLine. A public name used as Upstream would send forwarded traffic back toward the proxy instead of the application the guide calls the real address (https://docs.waf.chaitin.com/en/GetStarted/AddApplication).
The screen that confirms the fix has two parts, and both are required. First, repeat the SQL injection URL against your domain. The add-application guide says that if you see the blocking page, SafeLine defended the attack. That is the client-side confirmation of deny. Second, open the web console, find the event in the attack list, and click detail. Detail is the operator-side confirmation that this test was recorded, not a cached origin page or an unrelated browser error. The same guide lists XSS, path traversal, code injection, and XXE samples if you need a second payload, and it tells you to replace the sample host with your domain (https://docs.waf.chaitin.com/en/GetStarted/AddApplication).
Confirm allow with a clean request to the same domain and port, with no attack payload. The original application should load, which means the proxy accepted the request and forwarded it upstream. If the attack URL shows the blocking page and the attack detail, while the clean URL shows the application, allow and deny are separated for this entry. If the attack URL is blocked but the clean URL fails, deny is working and allow is not. Recheck Port, the SSL option on HTTPS applications, and Upstream. Do not loosen a deny test to make the allow path look healthy.
Why did my deny test show the origin page?
The domain was still aimed at the origin, so the request bypassed SafeLine. After DNS points at the SafeLine server, the same payload should produce the blocking page and a new attack-list event. An unchanged attack list means the fix is not confirmed yet.
Which screen confirms the deny, the block page or the detail view?
Use both. The blocking page confirms what the client received. The attack list, opened with detail, confirms that the console recorded the attack for the test you sent. Either screen alone can be mimicked by a cached page or by looking at the wrong event.
How do I confirm allow without turning deny off?
Send a normal request to the same Domain and Port, with no attack payload. A successful allow is the original application loading through SafeLine. Keep that check separate from the attack URL so a working block does not conceal a bad Upstream value.
Can I copy a custom allow and deny syntax from these pages?
No. The pages name a Web Access Control List and IP-based rate limiting, and they show how to add one application and how to read a block. They do not provide rule grammar, example allow entries, or a file to edit. Stay with the decision checklist until a later official page documents the editor.
What should I verify before the first test?
Verify Domain, Port, the SSL option for HTTPS, and Upstream, then verify that the domain resolves to the SafeLine server. Those are the documented inputs for one application. A wrong listener or a wrong upstream makes both the allow forward and the deny screen unreliable.
SafeLine has surpassed 700,000 installations worldwide as of September 30, 2026. SafeLine Pro annual promotional pricing is $650-$880, compared with the regular $1,000 per year.