> For the complete documentation index, see [llms.txt](https://www.osdeploy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.osdeploy.com/archive/go-osdcloud/proxies.md).

# Proxies

If you have made it this far, then you are ready to create your Proxies. Here are some examples

## any (Catch All)

At an absolute minimum, you should make a Catch All. This is used to redirect any traffic that does not match a route. Redirect to a Help page or to your Home page, either is a good choice

1. **Proxies**
2. **Add**
3. **Name: any**
4. **Route template: /{\*any}**
5. **Response override**
6. **Status code: 302**
7. **Status message: Temporary Redirect**
8. **Headers Name: Location**
9. **Headers Value: \<Home or Help page>**
10. **Create**

![](https://3996045416-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LDKRxGiKLYjW1gana2O%2Fuploads%2FsLCx5QBMKmtWeHTg3HFr%2Fimage.png?alt=media\&token=18cda260-e127-499e-b5f2-6af187b276f2)

{% code title="proxies.json" %}

```json
{
  "$schema": "http://json.schemastore.org/proxies",
  "proxies": {
    "any": {
      "matchCondition": {
        "route": "/{*any}"
      },
      "responseOverrides": {
        "response.statusCode": "302",
        "response.statusReason": "Temporary Redirect",
        "response.headers.Location": "https://osdcloud.com"
      }
    }
  }
}
```

{% endcode %}

## twitter

Here's an example of <https://go.osdcloud.com/twitter>

1. **Proxies**
2. **Add**
3. **Name: any**
4. **Route template: /twitter**
5. **Response override**
6. **Status code: 302**
7. **Status message: Temporary Redirect**
8. **Headers Name: Location**
9. **Headers Value: \<your Twitter profile>**
10. **Create**

![](https://3996045416-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LDKRxGiKLYjW1gana2O%2Fuploads%2FUvhzbQvvdgf41OHDjvRR%2Fimage.png?alt=media\&token=b169a30d-1929-4f72-9808-4e66d0c8f046)

{% code title="proxies.json" %}

```json
{
  "$schema": "http://json.schemastore.org/proxies",
  "proxies": {
    "any": {
      "matchCondition": {
        "route": "/{*any}"
      },
      "responseOverrides": {
        "response.statusCode": "302",
        "response.statusReason": "Temporary Redirect",
        "response.headers.Location": "https://osdcloud.com"
      }
    },
    "twitter": {
      "matchCondition": {
        "route": "/twitter"
      },
      "responseOverrides": {
        "response.statusCode": "302",
        "response.statusReason": "Temporary Redirect",
        "response.headers.Location": "https://twitter.com/SeguraOSD"
      }
    }
  }
}
```

{% endcode %}

## Editing proxies.json

If you are good with editing JSON files directly, you can absolutely do this in the Azure Portal

1. App Files
2. Select proxies.json from the combo box

![](https://3996045416-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LDKRxGiKLYjW1gana2O%2Fuploads%2FYblJvVhUrh89rnRzQY01%2Fimage.png?alt=media\&token=0dfade90-4c5c-4c98-b9bc-73d00694c5f5)

## Sponsor

**OSDeploy is sponsored by** [**Recast Software**](https://www.recastsoftware.com/?utm_source=osdeploy\&utm_medium=ad\&utm_campaign=web) **and their Systems Management Tools**

{% embed url="<https://www.recastsoftware.com/?utm_source=osdeploy&utm_medium=ad&utm_campaign=web>" %}
Sponsored by Recast Software
{% endembed %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.osdeploy.com/archive/go-osdcloud/proxies.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.