A suspicious request that reaches your application without a block does not immediately prove that your WAF missed the attack. First, establish whether the request passed through the WAF at all. A concrete configuration mistake is leaving the application domain pointed at the origin server after adding the application to SafeLine.
This guide explains how to test path traversal and XXE requests on a WAF while troubleshooting that routing mistake. The confirmation comes from two documented screens: the blocking page in the browser and the attack list in the SafeLine web console.
The misconfiguration: the domain still points to the origin
SafeLine operates as an HTTP/HTTPS reverse proxy. It receives application traffic, filters it, and forwards permitted traffic to the upstream application. Its application setup guide explicitly instructs administrators to resolve the configured domain to the IP address of the server running SafeLine. If the domain still resolves directly to the origin, those requests bypass that reverse proxy. Source: Protecting an application
Consider a controlled staging setup where you have added the application in SafeLine but have not updated its DNS record. Your browser still reaches the website, so the deployment appears functional. However, sending an attack-shaped request to that hostname tests the origin route rather than the intended WAF route.
Treat this as a troubleshooting scenario, not a reported test result. The objective is to collect evidence that the route has changed and that SafeLine handles the documented test requests.
Establish the route before testing detection
Use an application you own or have authorization to test, preferably in staging. Record the application hostname, the SafeLine server address, and the origin address.
In the SafeLine Web Admin Console, open Applications and inspect the configured application. The official setup guide defines three relevant settings:
- Domain identifies the application domain, hostname, or IP address.
- Port specifies the port SafeLine listens on; HTTPS applications require the SSL option.
- Upstream identifies the real application address to which SafeLine forwards traffic.
These settings and their meanings are documented in the application configuration guide.
Check the hostname's DNS resolution from the machine performing the test. For this scenario, the failure is concrete: the resolved destination is the origin instead of the SafeLine server. Correct the relevant DNS record so the application domain resolves to SafeLine, as required by that guide. Recheck resolution before proceeding; a cached answer can otherwise preserve the old route.
Load a normal application page after the change. Successful ordinary traffic provides a useful baseline before you introduce attack-shaped input.
Replay the documented requests
The official application guide supplies both path traversal and XXE examples as query-string requests. Replace its example domain with your authorized test hostname while retaining the documented test input:
- Path traversal uses the query value
id=../../../../etc/passwd.
- XXE uses the query value
id=<?xml+version="1.0"?><!DOCTYPE+foo+SYSTEM+"">.
These are the examples published in SafeLine's application testing instructions. Keep the hostname and route consistent between the normal request and each test request. Record the time and exact request so you can correlate the browser result with the console entry.
The XXE example is a documented detection probe. It does not establish that your application's XML parser expands external entities. Similarly, a traversal-shaped query does not establish that the application reads arbitrary files. Separate WAF request handling from application vulnerability testing when interpreting results.
The screens that confirm the fix
The official guide identifies a blocking page as evidence that SafeLine defended against its example attack requests. It also directs administrators to check the attack list in the web console and click "detail" to inspect a specific attack. Source: Test requests and verification
For this troubleshooting exercise, capture the browser blocking page and inspect the corresponding attack entry. Match the entry to the request you just sent using the available details. Repeat that verification separately for the path traversal and XXE probes.
The useful before-and-after record is specific: the hostname previously resolved to the origin; it now resolves to SafeLine; normal application access works; and each documented probe produces a blocking page with a corresponding console entry. A DNS change alone confirms only a configuration change. The request evidence confirms the tested behavior.
Does a successful application response prove that SafeLine was bypassed?
No. A successful response alone does not identify the route or explain the detection outcome. Check DNS resolution, application configuration, and the console evidence before assigning a cause.
Does the XXE probe prove that my application is vulnerable?
No. It tests how the WAF handles the supplied request pattern. Assessing XML parser behavior requires a separate application security test with its own controlled evidence.
What if DNS points to SafeLine but no blocking page appears?
The DNS bypass explanation is no longer sufficient. Recheck the configured domain, listening port, HTTPS SSL option, and exact request against the official guide. Inspect the attack list before drawing a detection conclusion; the supplied documentation does not provide a complete troubleshooting contract for every possible outcome.
What evidence should I retain after fixing the route?
Keep the before-and-after DNS observations, the application configuration, the exact requests and timestamps, the browser blocking results, and the corresponding attack details. That record supports a narrow, reproducible conclusion about these tests without claiming comprehensive protection against every traversal or XXE variant.
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.