Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 38 subscribers
  • Views 3769 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Redirect https traffic to server/port based on inbound url

Pete Matthews

Hi 

I'm not sure if this is possible and im getting confused between WAF's, NAT's and path specific routing...

What i'd like to achieve:

https://site1.mydomain.com is forwarded to https://internalserver:1234

https://site2.mydomain.com is forwarded to https://internalserver:1235

https://site2.mydomain.com is forwarded to https://internalserver:1236

Firstly is this possible or am i looking for a lost cause? 

Secondly, if it is possible, could you point me in the direction of an article or a video showing details on how to configure this. 

Thanks

Pete



This thread was automatically locked due to age.
Parents
  • 0

    Hi, 

    Thanks for the help. 


    I've got my WAF set up and it works well for two sub domains,  however i can only get OWA to respond / work when i set a NAT forwarding port 443 to my server. This then means my two waf's no longer fire. I'm assuming this isn't by design?

    Here is my config... can anyone spot an obvious mistake?

Reply
  • 0

    Hi, 

    Thanks for the help. 


    I've got my WAF set up and it works well for two sub domains,  however i can only get OWA to respond / work when i set a NAT forwarding port 443 to my server. This then means my two waf's no longer fire. I'm assuming this isn't by design?

    Here is my config... can anyone spot an obvious mistake?

Children
No Data
Unfiltered HTML