# Proxying Websites via Browser Settings

### Setup VGS Proxy in Firefox

Go to `Preferences` select the `General` tab. Under `Network Settings` select `Settings`. 

<figure><img src="/files/ssU7y9J3l6Ajawaum9ve" alt=""><figcaption></figcaption></figure>

Next, configure proxy settings as below:&#x20;

<figure><img src="/files/6Oc6Wwz1iuuApGbCWdjR" alt=""><figcaption></figcaption></figure>

You can also use PAC file to instruct the browser how to route traffic. ![pac file](/files/ByKoFTeImh6ds7aaelWD)

Put the PAC file url here:&#x20;

<figure><img src="/files/WkCVfZaMNTfU6oi3sd5T" alt=""><figcaption></figcaption></figure>

Go to your VGS dashboard and download the VGS certificate for your vault.&#x20;

<figure><img src="/files/tYBnZHwXGhiUDdoXlL9o" alt=""><figcaption></figcaption></figure>

To import the certificate into Firefox, go to `Privacy & Security` page in `Preferences` and choose `View Certificates`.&#x20;

<figure><img src="/files/Wpz9BTR3f8CYwNGTbaeI" alt=""><figcaption></figcaption></figure>

`Certificate Manager` window will pop up. Import the VGS certificate you just downloaded and it will show up in the list.&#x20;

<figure><img src="/files/ltD1jN8H9X9HWMjVDC8h" alt=""><figcaption></figcaption></figure>

When you try to access a site you will be prompted for the username and password for your VGS proxy. Under your VGS vault Settings page, you will find your access credentials. If you have not generated access credentials, then please generate and save for future usage. The access credentials will be used in Firefox's proxy authentication.&#x20;

<figure><img src="/files/Aj0gEFZI5EF2klTsLWGa" alt=""><figcaption></figcaption></figure>

In your vault dashboard, setup route and filter using regex for revealing card number in 6T4 token and CVC in Generic - Numeric Length Preserving format. You can use the yaml example for Progressive.com.

### Setup route for revealing a card

Enable `Access Logger` in your VGS dashboard. Setup an outbound route and put `(.*)` in the upstream host. If you do not have aliases, go to [VGS Vault API](https://github.com/verygoodsecurity/docs-content-vault/blob/update-content/api/vault/README.md) to create some.

On the ecommerce website checkout page, input the payment info with credit card number and CVC aliases of test cards.&#x20;

<figure><img src="/files/FoFwLKIsgFuJUnFKiKZh" alt=""><figcaption></figcaption></figure>

If the request passes the form validation and hits the payment gateway, you will see the result as below:&#x20;

<figure><img src="/files/JtguvU0yRPFaWS3UNJtS" alt=""><figcaption></figcaption></figure>

Go to your access logger and find the request coming in for that checkout. Check the information of that request and figure out what condition you should set to capture it. &#x20;

The body payload of progressive.com is in JSON format. Normally, you should be able to use `Secure this payload` to select the fields you want to reveal and set up filters directly.&#x20;

If you would like to make a more generic route, then please use a regex to filter your expressions.&#x20;

Once again, proceed to checkout with your credit card and CVC aliases. If you log in to your VGS Dashboard and select `Logs`, then you should see the transaction and be able to verify the aliases were updated with the real test card number and CVC.&#x20;


---

# 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.verygoodsecurity.com/vault/example-integrations/browser-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.