Using the Proxy

Configure your HTTP client to route through CIFP.

Any HTTP/S client that supports proxy configuration works with CIFP. This page shows the general pattern; see the sub-sections for language-specific examples.

Proxy URL Format

Your proxy URL is shown in the dashboard. It takes the form:

bash

https://proxy-id.proxy.cifp.vril.dev:3128

The proxy requires authentication. Use the username and password you generated on the Credentials tab. Most HTTP libraries accept proxy credentials either in the URL or as a separate option.

Proxy Credential in the URL

bash

https://username:password@proxy-id.proxy.cifp.vril.dev:3128

URL-embedded credentials are convenient for quick tests but avoid them in production since they may appear in logs or shell history. Use your client's dedicated proxy auth option instead (e.g. -U user:pass in curl, or proxiesdict with auth in Python requests).

Secret Placeholders

In auto-auth mode, send the placeholder syntax instead of the real credential:

bash

Authorization: Bearer {$MY_SECRET_NAME}

The proxy resolves MY_SECRET_NAME from its encrypted store and replaces the entire header value before forwarding. You can use placeholders in any header, not just Authorization.

Multiple placeholders in a single header value are supported:

bash

X-Custom: prefix-{$SECRET_A}:{$SECRET_B}

TLS in Firewall Mode

Firewall mode intercepts TLS. Download the CIFP mitmproxy CA certificate from your proxy's detail page and install it in your client's certificate store. Without this step, your client will reject the CIFP-issued TLS certificate.

bash

# Download CA cert for your proxy
curl https://cifp.vril.dev/api/proxies/proxy-id/ca-cert > cifp-ca.pem

# Tell curl to trust it
curl --cacert cifp-ca.pem -x https://proxy-id.proxy.cifp.vril.dev:3128 ...

# Or add to system trust store (macOS)
sudo security add-trusted-cert -d -r trustRoot -k /Library/Keychains/System.keychain cifp-ca.pem