IPIPD
Connection protocol and access control

How do I choose HTTP, SOCKS5, allowlisting, or credentials?

Start with the proxy protocols supported by your tool, then choose authentication based on whether the runtime has a stable public egress IP. The protocol controls how traffic is forwarded; authentication controls who may use the proxy.

Quick answer

Prefer HTTP when the tool explicitly supports it. Use SOCKS5 when the tool needs a more general TCP proxy and has verified SOCKS5 support. Consider IP allowlisting for a runtime with a stable public egress; credentials are usually easier when the egress changes or the setup moves between devices. The current product endpoint remains the authority for supported combinations.

HTTP versus SOCKS5

Prefer the protocol your target tool supports natively and can test clearly.

Tool supportHTTP proxyBrowsers, collection tools, and common HTTP clients are often straightforward to configure.SOCKS5 proxyThe tool or network library must explicitly support SOCKS5.
Forwarding modelHTTP proxyHandles HTTP requests and can tunnel HTTPS connections with CONNECT.SOCKS5 proxyForwards connections at a lower layer without interpreting HTTP content.
DNS resolutionHTTP proxyBehavior depends on both the client and proxy implementation.SOCKS5 proxySome tools can choose local or remote resolution; inspect the actual setting.
Selection ruleHTTP proxyPrefer it for web or API traffic when the tool supports it natively.SOCKS5 proxyUse it for general TCP proxying after compatibility has been verified.

Choose an authentication method

Allowlisting fits stable servers; credentials are often easier in changing networks.

01

Stable server egress

When a server has a fixed public egress IP, allowlisting can avoid distributing proxy passwords inside the application.

Allowlist the actual public egress IP

02

Changing or multi-device environments

Home, mobile, or multi-location networks can change egress addresses, making username/password authentication easier to move.

Store credentials securely and isolate them by environment

03

Teams and automation

Where supported, assign traceable authentication settings by workload instead of sharing plaintext credentials that cannot be audited.

Grant only the access the workload needs

General connection flow

Treat protocol, endpoint, port, and authentication as one configuration set.

  1. 01

    Select a protocol supported by the tool

    Do not place an HTTP endpoint in a SOCKS5 field or switch protocols only because the target URL uses HTTPS.

  2. 02

    Copy the proxy host and port

    Use the endpoint from the proxy list, extraction result, or setup page, and rule out spaces, expired records, or a mismatched port.

  3. 03

    Configure the authentication mode in use

    For allowlisting, verify the public egress IP. For credentials, verify field order, exact characters, and authorization scope.

  4. 04

    Verify egress with a minimal request

    Use a stable test target to confirm connectivity, egress IP, and target region.

  5. 05

    Run a small business-level test

    Only after connectivity works should you test the real target, so target rejection is not confused with proxy authentication.

Troubleshoot authentication

Separate authentication errors, network timeouts, and target-site rejection.

Use the symptom to locate the failing layer:

  • 407 Proxy Authentication Required: recheck credentials, allowlisting, and the authentication mode supported by the endpoint;
  • timeout while opening the proxy connection: inspect protocol, host, port, local firewall, and network egress;
  • proxy connection succeeds but the target request fails: inspect target policy, request rate, TLS, DNS, and workload parameters;
  • allowlisting fails intermittently: confirm whether NAT, an ISP, or the cloud platform changes the public egress.