Java Proxy Setup: HttpClient, Authentication and SOCKS
Java proxy configuration depends on the client that opens the connection. For java.net.http.HttpClient, begin with an explicit ProxySelector, a connection timeout and a request timeout. A SOCKS endpoint requires a client and configuration path that actually support SOCKS; an HTTP proxy example is not a SOCKS recipe.
Configure the client that sends the request
Create one HttpClient for a consistent proxy configuration and reuse it for that route. Set the selector with HttpClient.newBuilder().proxy(ProxySelector.of(new InetSocketAddress(host, port))). Add a connect timeout to the builder and a timeout to the HttpRequest. Read Oracle’s HttpClient builder reference for the API contract.
This Java 11+ example uses an HTTP proxy with an approved source-IP allowlist or no authentication. A completed HTTP response is a connectivity result; verify the exit separately.
// Java 11+; HTTP proxy using an approved source-IP allowlist or no authentication.
import java.net.InetSocketAddress;
import java.net.ProxySelector;
import java.net.URI;
import java.net.http.HttpClient;
import java.net.http.HttpRequest;
import java.net.http.HttpResponse;
import java.time.Duration;
public final class ProxyCheck {
public static void main(String[] args) throws Exception {
String host = System.getenv("PROXY_HOST");
String portValue = System.getenv("PROXY_PORT");
if (host == null || host.isBlank() || portValue == null) {
throw new IllegalArgumentException("Configure PROXY_HOST and PROXY_PORT");
}
int port = Integer.parseInt(portValue);
if (port < 1 || port > 65535) {
throw new IllegalArgumentException("Invalid proxy port");
}
HttpClient client = HttpClient.newBuilder()
.proxy(ProxySelector.of(new InetSocketAddress(host, port)))
.connectTimeout(Duration.ofSeconds(10))
.build();
HttpRequest request = HttpRequest.newBuilder(URI.create("https://example.com/"))
.timeout(Duration.ofSeconds(20))
.GET()
.build();
HttpResponse<Void> response = client.send(request, HttpResponse.BodyHandlers.discarding());
System.out.println("HTTP status: " + response.statusCode());
}
}
Keep proxy credentials separate from target credentials
Proxy authentication answers a request from the intermediary, while target authentication belongs to the API or website. If an Authenticator supplies a password, restrict it to the expected proxy host, port and PROXY requestor type. Load the values from protected configuration, and do not print them in diagnostic messages.
Treat HTTP and SOCKS as separate implementations
Do not infer SOCKS support from the fact that the JVM has networking properties or a Proxy.Type.SOCKS enum. Check the particular library and connection API. Document whether hostname resolution happens locally or on the proxy. The HTTP versus SOCKS5 comparison helps choose the required protocol before writing code.
Classify the result before retrying
Separate failures to connect, connection timeouts, interrupted requests and completed HTTP responses. A destination 403 or 429 is not automatically a dead proxy, and a 407 is a proxy authentication response. Record the status, elapsed time and redacted endpoint identity. Retry only where the operation and policy allow it, with a small budget and backoff.
Verify from the actual Java worker
Use a controlled IP-check URL first and validate the response content, not just a 200 status. Repeat the test from the same host that will run the application, then test the intended API. An online checker uses its own route. Keep TLS verification enabled, bound concurrency and retain the original failure category when escalating. See proxy-aware API testing for a test plan.
Frequently asked questions
Why do proxy requests timeout?
The proxy may be offline, slow, blocked, or configured with the wrong protocol or authentication.
Should I rotate proxies on every request?
Not always. Rotation should match the task. Sessions often need stable IPs.
How do I debug proxy code?
Start with one proxy, one simple URL, verbose logging, and short timeouts.
Do JVM proxy properties affect every Java library?
No. Each client may use its own connection and proxy configuration.
Is a connection timeout a total request deadline?
No. Configure the request timeout separately and understand the client's timeout contract.
Should I disable TLS checks to fix proxy errors?
No. Investigate the certificate chain and connection path instead.
Order clarity
What you receive
- What you receive
Proxy connection details for the package processed through the live order form.
- Protocols
HTTP or SOCKS5 options are shown during configuration for supported packages.
- Authentication
Set the requested proxy credentials during configuration before checkout.
- Locations
Current location availability is shown in the selector and can change with inventory.
- Support and checking
Support can help verify connection details and review replacement requests under the service policy.