Make Restlet's ClientResource Use the Proxy Connector You Configured

A configured Client has no effect on a ClientResource that still uses another connector. For Restlet 2.4.4's org.restlet.ext.httpclient helper, wire the resource to that client before starting it:

Client connector = new Client(new Context(), Protocol.HTTPS);
connector.getContext().getParameters().set("proxyHost", "proxy.example");
connector.getContext().getParameters().set("proxyPort", "8080");

ClientResource resource = new ClientResource(
    "https://service.example/status");
resource.setNext(connector);
connector.start();
try {
    String body = resource.get().getText();
} finally {
    resource.release();
    connector.stop();
}

setNext(connector) is the attachment point. The context uses the helper's documented proxyHost and proxyPort keys, with the hostname separate from its scheme and port. Set them before connector.start(). For a public HTTP endpoint, these two fields take an address and port from the HTTP proxy list.

This assumes the deployed helper is the stated Apache extension. It can also obtain defaults from JVM http.proxyHost and http.proxyPort; explicit context values make this connector's endpoint visible.

The example consumes the text body, releases the resource and stops the connector. A streaming use must likewise consume or release its representation so pooled connections can be released.