Manage cookies that are used for advertising, such as ad personalization, remarketing, and ad effectiveness analysis.
2.4.1.2.11. Access to site when using traffic filtering service
flowchart LR
request@{ shape: stadium, label: "➡️ Request" }
filter@{ shape: rect, label: "🛡️ Filtering service" }
site@{ shape: stadium, label: "✅ Site" }
access@{ shape: diamond, label: "Access
allowed?" } error@{ shape: stadium, label: "🚫 Error 403" } request-->filter-->site request-->|Bypassing
filtering
service|access-->|Yes|site access-->|No|error
allowed?" } error@{ shape: stadium, label: "🚫 Error 403" } request-->filter-->site request-->|Bypassing
filtering
service|access-->|Yes|site access-->|No|error
When using the traffic filtering service, you can allow or deny access to the site from other IP addresses that are not associated with the filtering service. This allows you to protect the site from requests that bypass the filtering service.
Conditions
The configuration option is only available under the following conditions:
- The site uses one of the supported traffic filtering services: Cloudflare, Deflect, DDoS-Guard, Qrator, QUIC.cloud or our protection service.
- Traffic filtering is enabled on the traffic filtering service side.
- Our system has identified the traffic filtering service being used (see Site access logs (Access log)).
Configure
The traffic filtering service in the setting name corresponds to the service identified by our system.
The configuration is performed in the "Site protection" section on the "Main settings" tab:
- Deny other IPs to connect to the site — the site will only be accessible from the IP addresses of the traffic filtering service, others will get an error 403.
- Allow other IPs to connect to the site — the site will be accessible from any IP addresses.
(1)