Choose clj-http’s Proxy Configuration Level

For clj-http 3.13.1, start with the library’s documented Java-property and request-map interfaces. A desktop proxy preference alone does not show which settings the application supplied.

A request can select an HTTP intermediary explicitly:

(require '[clj-http.client :as http])

(http/get "https://example.com/"
          {:proxy-host "proxy.example.net"
           :proxy-port 8080})

For a common JVM policy, clj-http documents http.proxyHost and http.proxyPort for HTTP destinations, plus https.proxyHost and https.proxyPort for HTTPS destinations. The shared bypass property is http.nonProxyHosts.

Explicit proxy-host and proxy-port options override that property-based route, including http.nonProxyHosts. For an allowed public test configuration with no proxy credentials, an HTTP entry from the HTTP proxy list can supply the request’s host and port. clj-http also exposes proxy-ignore-hosts for request-level exclusions; its documented default contains localhost and 127.0.0.1.

When the intermediary needs credentials, supply proxy-user and proxy-pass in the request options from the application’s credential source.

SOCKS has a separate interface: create a manager with clj-http.conn-mgr/make-socks-proxied-conn-manager and pass it as connection-manager. Reuse and shut down that manager according to the workload’s lifecycle.