# Installing a Stand-alone Built in Forwarding Proxy A built in forwarding proxy is a networking component and as such can be installed within your network between your load balancer and your existing application servers (such as Microsoft IIS or Apache with PHP). As a general rule, you should have one built in forwarding proxy for each application server in your network. The built in forwarding proxy can co-exist on the same operating system as your existing application server, provided you configure non-conflicting ports and proper forwarding instructions in your server definitions. The most important step in the configuration is to ensure that requests from the load balancer to the built in forwarding proxy are routed correctly. If your load balancer does not perform SSL termination, you will also be required to configure the built in forwarding proxy to correctly serve up your SSL certificate. The process of creating and configuring a built in forwarding proxy involves a large number of steps and therefore have been relegated to its own section [**Creating a stand-alone built in forwarding proxy**](/cap/product-reference/creating-a-stand-alone-built-in-forwarding-proxy.md)**.** --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.tomorrowx.com/cap/product-reference/installation-and-configuration/installing-a-stand-alone-built-in-forwarding-proxy.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.