ProxyPass /crm http://crm.example.com/ ProxyPass /bugzilla http://backend.example.com/bugzilla A reverse proxy can provide a unified frontend to a number of backend resources, associating certain URLs on the frontend machine to specific backend web servers. For example, you may have one server running a CRM application and another one running a bug tracking tool. Whenever your users need to use one application, they need to type a different address. You could integrate these services with your main site using ProxyPass, as shown in the example. Now, when the reverse proxy machine receives a request for http://www.example.com/crm/login/index.html, it will request http://crm.example.com/login/index.html from the backend server and return the document to the browser. The ProxyPass directive can be used standalone or inside a <Location> container, as in the following example: <Location /crm> ProxyPass http://crm.example.com/ </Location> Finally, you probably want to use ProxyPass together with ProxyPassReverse, described in the following section. |