By now, many of you have seen the articles that discussed Address Book Policies, hosting changes, and the Hybrid Configuration Wizard, but deep down I know you all have been hoping that we would di...
Updated Jul 01, 2019
Version 2.0
Blog Post
Hi. Great to have finally silent cross site redirect, thanks!!
Now please try to think about something more - Internal redirect. Why I am asking for it. Imagine company that wants single global URL for OWA hooked to the largest datacenter. However there are lots of small sites, with or without internet connectivity, connected by limited WAN to the central site. What happens i.e. if user from non-internet facing site hits the global OWA now?
1. User logs to central OWA thorough WAN
2. Central OWA proxies request to the user`s site OWA, thorough WAN back
3. Request is returned to central proxying OWA and then again to the user, 2x thorough WAN
So the information requested has traveled four times thorough WAN, because we don’t have internal redirect. If the user`s site has internet connectivity (and ExternalURL), then user will be redirected to it. So the user will not connect internally but i.e. thorough local proxy. It’s still better than WAN ping pong but not ideal.
I understand, that there is a problem how to distinct user connecting internally requiring internal redirect. Well I hope simple IP range definition of from where external/internal connection goes can leverage that.
Thanks in advance.
David