How to configure proxy settings in browser and client apps

Quick answer: Configure the program that opens the network connection: a browser profile, operating-system setting, extension, command-line client, or application can use a different route. Set the proxy and bypass rules there, then verify from that same program. A working curl request does not prove the browser uses the proxy.

Warning: Start with an owned sandbox endpoint and an authorized test route. A production check requires explicit permission and a fixed traffic allowance. Send one request and stop; traffic charges may apply. Keep proxy credentials out of saved commands, URLs, screenshots, and logs.

Find the owner of the network connection

Do not assume a third-party “proxy manager” or extension makes all applications use the same route. If it supplies a PAC script or per-domain rules, inspect what happens to the exact destination. If it asks for provider credentials, check how those are stored and who can read exported profiles. A list of public proxy addresses is not an acceptable replacement for a trusted endpoint with known ownership.

Run a curl route check

Prerequisites: The shell example passes bash -n with Bash 3.2.57 on macOS. curl 8.7.1 is installed for the proxy request; a successful request requires an authorized endpoint. Install Bash from the official GNU Bash page and curl from the official curl download page if needed. Set PROXY_URL to the credential-free scheme, host, and port supplied for an unauthenticated or source-IP-allowlisted route. Set TARGET_URL to one permitted HTTPS endpoint. Do not include a username or password in either value.

: "${PROXY_URL:?Set PROXY_URL to a credential-free proxy URL}"
: "${TARGET_URL:?Set TARGET_URL to one permitted HTTPS endpoint}"

curl --disable --proxy "$PROXY_URL" --noproxy '' \
  --connect-timeout 10 --max-time 25 \
  --silent --show-error --output /dev/null \
  --write-out 'target=%{response_code} connect=%{http_connect}\n' \
  "$TARGET_URL"

Illustrative output for a successful HTTP CONNECT request:

target=200 connect=200

These are response statuses for this client request, not proof of another application’s route.

A successful target status shows that this curl process reached the endpoint through the configured route. For HTTP proxies, connect=200 records an accepted CONNECT tunnel. SOCKS routes do not use HTTP CONNECT, so the connect field is not a SOCKS success test. The check does not prove that a browser profile or another application uses the same path.

Run a two-part check

Open a fixed HTTPS destination from the intended program. Use a trusted IP echo endpoint to inspect the application's observed exit, then test the actual allowed target and check its final URL and content. Compare with a second application only to identify a mismatch. A direct curl connection alongside a proxied browser does not invalidate the browser's routing.

If HTTP works and HTTPS fails, check whether the proxy supports CONNECT and whether the browser has an HTTPS proxy entry. If some hosts bypass while others use the proxy, inspect exclusion lists, PAC conditions and local-network defaults. If authentication fails with 407, use the proxy auth guide. Keep credentials out of command-line flags and screenshots.

For a profile-oriented browser such as AdsPower or Octo, use its own profile setup guide; changing Windows settings may not change an existing browser profile.

For an Octoparse task, its current proxy guide places the routing choice under Task Settings → Anti-blocking → Access website via proxies. Use my own proxies applies to local runs, accepts HTTP host:port entries and does not support username/password authentication; cloud runs use Octoparse's built-in proxies. The proxy configured on the login screen only affects login, not task extraction. Example: if a local task returns the expected record using an IP-allowlisted HTTP endpoint but the same task in cloud does not, changing the login proxy cannot fix cloud egress. Check the cloud task's built-in proxy selection, region and output independently. Do not paste a user:password@host URL into the own-proxy field expecting authentication.

ProxyLaneTraffic never expires

Premium residential proxies
From $2/GB

Scale your workflows with the tools you already use. Rotating or sticky sessions up to 72 hours.

Try 350 MB for $1.95 View plans