> For the complete documentation index, see [llms.txt](https://docs.verygoodsecurity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verygoodsecurity.com/vault/http-proxy/operations/redacting-files-via-the-https-proxy.md).

# Redacting Files via the HTTPS Proxy

You can redact any file through VGS HTTP proxy by sending this file in your request. For example to redact an image:

1. Convert an image into the base64 format.
2. Create JSON file with the base64 text of the image.
3. Create a new inbound route in VGS dashboard with default settings. Add the field from your file in JSON path in the filter section to redact this particular field.

![redact\_through\_http](https://2096104711-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUreALQAfVnRMQEz110rC%2Fuploads%2FlhdqYVngFEveo47IewBD%2FScreenshot%202026-08-05%20at%202.48.39%E2%80%AFPM.png?alt=media\&token=a724362b-5a75-443c-ba20-70c243205338)

4. Use this curl request in order to send an image to VGS proxy:
   1. NOTE: The intended value for `<VAULT_ID>` is the **Tenant ID** (also known as *Vault ID*), beginning with prefix *tnt*.

```bash
curl https://<VAULT_ID>.<ENVIRONMENT>.verygoodproxy.com/post \
    -H "Content-type: application/json" \
    -d @ABSOLUTE_PATH_TO_JSON_FILE
```

5. To make sure request was sent successfully, monitor routes activity via the [Logs](/vault/http-proxy/access-logger.md) page.&#x20;

<figure><img src="https://2096104711-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUreALQAfVnRMQEz110rC%2Fuploads%2Fp1KbvX6Ftq4f6oDOwOYj%2FScreenshot%202026-08-05%20at%202.34.05%E2%80%AFPM.png?alt=media&amp;token=22169fe0-86fc-4577-8330-99c2123a9223" alt=""><figcaption></figcaption></figure>

You can upload files up to 24MB in size. The [Vault API](/vault/developer-tools/apis/vault-api.md) supports files up to 32MB in size.


---

# 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://docs.verygoodsecurity.com/vault/http-proxy/operations/redacting-files-via-the-https-proxy.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.