# Adding a proxy

{% hint style="info" %}
**Info:** by default, the extension has some proxies pre-defined and you don't need to host your own if you don't like. This has been explained more in detail at the following link: [proxy-information](https://wiki.cdn-perfprod.com/must-read/proxy-information "mention").
{% endhint %}

## :computer: How to add a proxy server to the extension

***

We need to access the Extension's options page, to do so: click on the extension's icon (located at the puzzle icon) and click on <mark style="color:red;">**Options.**</mark>

<figure><img src="https://3089871892-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fw0DtUs3tWZJZTa0QKQCG%2Fuploads%2Fi8l29xLQtAgR52yq9gh4%2FScreenshot_153.png?alt=media&#x26;token=6321d250-20da-462e-9a17-fa8dcb90b3d9" alt=""><figcaption></figcaption></figure>

Now in the extension's options page you'll see a Proxies tab in which you'll be able to add proxies to the Proxy ad requests segment or the Proxy all requests segment. Primary proxies are priorized over fallback, and fallback proxies are only used if the proxy above it fails to respond to a request (is down).

{% hint style="success" %}
**Proxy ad requests:** will optimize and only proxy what's strictly needed to avoid Twitch's ads. This method will reduce significatively the bandwidth usage on the server's end.
{% endhint %}

{% hint style="warning" %}
**Proxy all requests:** will just proxy all required requests all the time without analyzing which ones are needed or not to avoid the ads. This method does use more bandwidth than Proxy ad requests but can be considered more reliable.
{% endhint %}

In the following example image you'll see that the Proxy ad requests option is enabled and there's 2 proxies added. This means that by default it will proxy to the first one (beta.eu) and alternatively, if the first one is down, it will proxy to the next one (eu).

The proxy all requests option which is currently disabled does in reverse because I added them like that.

<figure><img src="https://3089871892-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fw0DtUs3tWZJZTa0QKQCG%2Fuploads%2FKrNqkLqYn9cq5E166y6a%2FScreenshot_156.png?alt=media&#x26;token=f023d3ab-32bc-4e26-a6ef-6f92bcf64119" alt=""><figcaption></figcaption></figure>

For more advanced settings please go to the following page:

{% content-ref url="../../advanced/options-page" %}
[options-page](https://wiki.cdn-perfprod.com/advanced/options-page)
{% endcontent-ref %}


---

# 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://wiki.cdn-perfprod.com/guides/extension/adding-a-proxy.md?ask=<question>
```

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.