> For the complete documentation index, see [llms.txt](https://docs.tomorrowx.com/cap/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tomorrowx.com/cap/product-reference/concepts-and-terminology/proxies.md).

# Proxies

<code class="expression">space.vars.X\_Product\_Name</code> is a very network centric product. As such there are a number of network level definitions that can be confusing - especially when it comes to the large number of potential proxies being involved. The following is a list of the terms used for various proxies within and used by the product.

## Web proxy

A web proxy is a proxy server that is installed as a performance optimizer or security feature between <code class="expression">space.vars.X\_Product\_Name</code> and the World Wide Web. Typically, this is a corporate proxy that <code class="expression">space.vars.X\_Product\_Name</code> must traverse to access services such as the update server, MaxMind, SMS services etc.

## Composable Agentic Platform built in proxy (forwarder)

The built in <code class="expression">space.vars.X\_Product\_Name</code> proxy, called Proxy Server in the console, is a forwarding proxy used to protect sites that are unable to take advantage of the inline filter *(e.g. all non-J2EE sites)*. It is also used to test <code class="expression">space.vars.X\_Product\_Name</code> rules against any site, without performing any installation. The latter is achieved using the built in browser proxy.

## Browser proxy

The browser proxy is a feature of the built in forwarding proxy. The browser proxy allows configuration of a proxy within browser settings and have the requests from that browser sent through the <code class="expression">space.vars.X\_Product\_Name</code> built in proxy. This provides a convenient method for testing rules against sites without installing any additional software.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.tomorrowx.com/cap/product-reference/concepts-and-terminology/proxies.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.