Skip to content

Using Pipeleek with Proxies

Pipeleek supports routing all HTTP/HTTPS traffic through a proxy server. This is useful for:

  • Traffic interception: Analyze API calls with tools like Burp Suite or mitmproxy
  • Internal network access: Connect to internal GitLab/Gitea/... instances through SOCKS5 proxies

Proxy Configuration

Pipeleek uses the standard HTTP_PROXY environment variable for proxy configuration.

1
HTTP_PROXY=http://127.0.0.1:8080 pipeleek gl scan -g https://gitlab.com -t glpat-xxxxx

SOCKS5 can be used as well.

1
HTTP_PROXY=socks5://127.0.0.1:1080 pipeleek gl scan -g https://gitlab.internal.company.com -t glpat-xxxxx

Ignoring Proxy Configuration

In some environments, HTTP_PROXY may be set system-wide but you don't want Pipeleek to use it. Use the --ignore-proxy flag to bypass proxy detection:

1
HTTP_PROXY=http://127.0.0.1:8080 pipeleek --ignore-proxy gl scan -g https://gitlab.com -t glpat-xxxxx

TLS/SSL

Pipeleek automatically skips TLS certificate verification (required for self signed certificates).