![web application proxy vs reverse proxy web application proxy vs reverse proxy](https://www.jgspiers.com/wp-content/uploads/2018/08/47-min.jpg)
![web application proxy vs reverse proxy web application proxy vs reverse proxy](https://res.cloudinary.com/practicaldev/image/fetch/s--e5RXtRIx--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/http://remyg.ovh/assets/img/reverse-proxy.png)
There has been a lot of discussion about where it should be placed. WAP can be in the internal network or DMZ. This is a high level overview of using a Web Proxy with Exchange OWA. You should be presented with the Exchange OWA page and it should be using the correct certificate as well. Once complete, you can now launch a web browser and enter in the External URL you specified in the previous step. On the confirmation page, double check that you are happy with everything and then click Publish. Once you have filled in everything, you can then click the Next button.
#Web application proxy vs reverse proxy how to#
I will not go into detail on how to set up Active Directory Federation Services (ADFS) as that is outside the scope of this discussion. A Web Application proxy works with Active Directory Federation Services (ADFS). What is a Web Application Proxy (WAP)? It gives you reverse proxy functionality for web applications such as Outlook on the web (OWA). (Disclaimer: I have not tested it yet on this version with Exchange 2016 or Exchange 2019). I have used the Web Application Proxy (WAP) in Server 2012 R2, Server 2016 and Server 2019 and I see it is applicable to Server 2022. In this article I will discuss another option you can use: a Web Application Proxy.
![web application proxy vs reverse proxy web application proxy vs reverse proxy](https://i.stack.imgur.com/E5qyk.png)
In one of my previous posts, I briefly spoke about load balancers to be the front facing option instead of having your Exchange servers exposed to the internet.