> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bigdata.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Proxy configuration

<Warning>
  We are sunsetting our SDKs and will no longer add new features, security patches, bug fixes, or technical support for them. To access the latest capabilities and ongoing improvements, we encourage you to migrate to our [RESTful API](/api-rest/introduction).

  SDK support will officially end on **December 31, 2026**. On this date, the underlying endpoints used by the SDKs and related documentation will be decommissioned.

  To avoid any disruption to your services, please ensure your migration is complete by that date.

  For migration assistance, please contact us at [support@bigdata.com](mailto:support@bigdata.com).
</Warning>

Bigdata supports a proxy setup on the client's side. By setting a proxy
you can redirect output traffic and work with it before it leaves your
network. This is useful for debugging, security, and privacy reasons.

# Set up

The recommended approach uses the standard environment variables: `HTTP_PROXY`, `HTTPS_PROXY`, and `WSS_PROXY`.

However, the Bigdata object also supports a proxy parameter. Please choose only one of the two approaches.

<Tabs>
  <Tab title="Proxy environment variables">
    Example with environment variables:

    ```bash theme={null}
    export HTTPS_PROXY="http://127.0.0.1:3128"
    export WSS_PROXY="http://127.0.0.1:3128"
    ```

    <Warning>
      Environment variable **ALL\_PROXY** is not supported.
    </Warning>
  </Tab>

  <Tab title="Proxy as Bigdata parameter">
    Example with proxy as Bigdata parameter:

    ```python theme={null}
    bigdata = Bigdata(proxy=Proxy(protocol="all", url="http://127.0.0.1:3128"))
    ```
  </Tab>
</Tabs>

<Tip>
  In the case of proxies with credentials use the following format:

  ```bash theme={null}
  HTTPS_PROXY="http://user:pass@127.0.0.1:3128"
  ```
</Tip>