Help Center/ Web Application Firewall/ User Guide (Kuala Lumpur Region)/ FAQs/ Website Domain Name Access Configuration/ Operations After Connecting Websites to WAF/ How Can I Forward Requests Directly to the Origin Server Without Passing Through WAF?
Updated on 2024-03-14 GMT+08:00
View PDF
Share

How Can I Forward Requests Directly to the Origin Server Without Passing Through WAF?

If you select Cloud for Protection, take the following steps to route your website traffic to origin servers.

If you select Cloud - CNAME or Dedicated for Protection, take the following steps to route your website traffic to origin servers.
  • Cloud

    Switch the WAF working Mode to Bypassed. Then, your website requests directly go to the origin servers without passing through WAF. It takes about 3 to 5 minutes for WAF bypass to take effect.

  • Dedicated mode
    • If your website has a private network load balancer deployed behind the dedicated WAF instance, as shown in Figure 1, unbind the EIP from the internet-facing load balancer and then bind the EIP to the private load balancer. In doing so, your website traffic will bypass WAF and directly go to the origin server.
      Figure 1 Dedicated WAF instance deployment architecture (private network load balancers deployed behind dedicated WAF instances)
    • If your website has no private network load balancer deployed behind the dedicated WAF instance, as shown in Figure 2, unbind the EIP from the dedicated WAF instance and then bind the EIP to the origin server. In doing so, your website traffic will bypass WAF and directly go to the origin server.
      Figure 2 Dedicated WAF instance deployment architecture (no private network load balancer deployed behind dedicated WAF instances)