inbound routing based on request URI - possible?

can I send requests for http://dave.com to 192.168.1.5 and http://john.com to 192.168.1.6?

I have the firewall WAF rule setup to match a particular website name, but because the inbound NAT rule is processed first and is bound to only the port, i.e. 80 and then you must specify the destination, i.e. 192.168.1.5 - I can't see a way around this? (maybe it was never possible)

Cheers

R

Parents
  • Hi Ryan,

     

    If you want two different backend servers to handle the two different URIs, then the easiest solution is to have two separate WAF rules, one for each domain you want to host. Then in each WAF rule you can specify which backend server will be used to handle the request.

     

    In this scenario, you don't need the NAT rule, only the two WAF rules. Following your example, the setup will look like this:

    In WAF rule #1 the domain is set to dave.com, web server is set to 192.168.1.5.

    In WAF rule #2 the domain is set to john.com, web server is set to 192.168.1.6.

     

    With this setup all HTTP requests on port 80 that was sent to dave.com will be routed to 192.168.1.5, requests sent to john.com will be routed to 192.168.1.6. Requests sent to any other domain will not be handled.

     

    Regards,

    Attila

     
Reply
  • Hi Ryan,

     

    If you want two different backend servers to handle the two different URIs, then the easiest solution is to have two separate WAF rules, one for each domain you want to host. Then in each WAF rule you can specify which backend server will be used to handle the request.

     

    In this scenario, you don't need the NAT rule, only the two WAF rules. Following your example, the setup will look like this:

    In WAF rule #1 the domain is set to dave.com, web server is set to 192.168.1.5.

    In WAF rule #2 the domain is set to john.com, web server is set to 192.168.1.6.

     

    With this setup all HTTP requests on port 80 that was sent to dave.com will be routed to 192.168.1.5, requests sent to john.com will be routed to 192.168.1.6. Requests sent to any other domain will not be handled.

     

    Regards,

    Attila

     
Children