I have v9 running in front of an Exchange 2013 server. The real server is internal.example.com and the virtual server is mail.example.com. When I point my browser at https://mail.example.com/ecp/ I get a response but then the url changes to https://internal.example.com/ecp/blahblah and everything stops since that address is not in DNS outside the LAN.
If I point to https://internal.example.com/ecp/ from the internal LAN everything works. Which should be obvious since I am not hitting the firewall.
If I turn off WAF and use NAT port forwarding, address https://mail.example.com/ecp/ works just fine and stays as mail.example.com.
All the virtual directories in Exchange are configured for the external address.
Thoughts on what is going on or ideas how to troubleshoot?
I had the same issue with sharepoint redirecting to an internal URL any time I referenced the server by internal IP. It seems as though sharepoint would rewrite the URL of the hostname that was sent to the server. So, whatever you use as an IP or DNS specification on the real server identification will be used as the return domain name. What I ended up doing was creating a static URL entry on the DNS server of the UTM to point the external domain name to the internal IP address. This allows the UTM to point to the server by the external name using an internal IP address. It worked for SharePoint (2010) and may be the same for this.
Users permitting: Set static entry for external DNS name to internal IP in Network Services -> DNS Set the Real Server's host record to a DNS record type of the external name.
Check Check Check the site afterwards... SharePoint did STRANGE things with uploading files and different views. I ended up just NATting the thing instead of spending time figuring it out.
I checked the box for "Pass Host Header" and now the url is staying as the external. Now to just figure out authentication. Type in credentials and get presented with same login page.
Lol, should've edited my original post... that's what I was referencing in the options. Have fun figuring the rest out. I don't think there are enough options in WAF to suffice for everything out there. You may want to wait for v9.1 I here they are fixing problems with RPC over HTTP and WAF. Link (I recall BAlfson calling out developers to get that pushed in to 9.1).
Quote