# Web Proxy

When you deploy Reblaze to protect your web assets, it acts as a proxy, receiving requests from clients (web visitors, mobile/native app users, etc.), blocking hostile traffic, and passing legitimate requests to your servers.

The Web Proxy section defines how Reblaze behaves in this role. It consists of three tabs: 

* [General Settings](https://waap.docs.link11.com/v2.12.0/product-walkthrough/settings/web-proxy/web-proxy-general-settings)
* [Application Profiles](https://waap.docs.link11.com/v2.12.0/product-walkthrough/settings/web-proxy/application-profiles)
* [Security Profiles](https://waap.docs.link11.com/v2.12.0/product-walkthrough/settings/web-proxy/security-profiles)

Proxy settings are configured per site/application. To switch between them, click on the drop down menu on the right side.  

![Proxy Settings](https://3134296238-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LuRghgerfT6t9aVOOha%2F-Lvu4tbFqMGHEhH3jyoo%2F-Lvu6xgHebjMvncFhzoi%2Fimage.png?alt=media\&token=c624784f-c2df-41e1-8891-a017c3808484)

After making edits to this section, don't forget to [Save Changes and Publish](https://waap.docs.link11.com/v2.12.0/using-the-product/best-practices/publish-your-changes) them to the cloud.