Proxy, certificates and HTTP/2
How requests reach the network: through a company proxy or not, which servers are trusted, which certificate CLEM shows a server that asks for one, and which HTTP version it speaks.
Proxy
Settings → Proxy:
| Mode | Does |
|---|---|
| System (default) | Follows your operating system: its proxy settings, a PAC script or automatic detection. A company proxy usually works without setup. |
| None | Always connects directly. |
| Manual | Sends every request through one proxy (http://host:port or https://host:port), except to the hosts in Bypass for. |
If the proxy asks for a login, enter the user name and password under Manual; the password is stored encrypted on this computer. Logs and reports show which proxy a request used, never the password. SOCKS proxies and Windows-integrated logins (NTLM / Kerberos) aren't supported.
The same setting covers Test Request, OAuth 2.0 token requests and the sign-in window. Exported scripts follow HTTPS_PROXY, HTTP_PROXY and NO_PROXY, like most command-line tools, or --proxy:
HTTPS_PROXY=http://proxy.corp:8080 NO_PROXY=localhost,.corp node my-flow.js
node my-flow.js --proxy http://user:pass@proxy.corp:8080 --proxy-bypass "localhost, .corp"
node my-flow.js --proxy none
Certificates
Settings → Certificates decides which servers are trusted, and which certificate CLEM shows a server that asks for one.
Trusting servers
- Trust this computer's certificate store (on by default) trusts what your operating system trusts, as your browser does: company CAs and the roots of TLS-inspecting proxies installed in Windows, the macOS keychains or the Linux CA bundle just work. The panel shows what was read; Reload reads the store again after a CA was installed.
- Add CA Certificate: your company's or an internal CA (PEM or DER). Servers with a certificate it signed are verified like public ones. This is the right answer where "accept invalid certificates" is the wrong one.
Client certificates (mTLS)
Add Client Certificate: a certificate and key (PEM files) or one PFX / P12 file, offered to the servers of one host (api.bank.com), its subdomains (*.bank.com) or every host (*) when they ask for one. The first matching row wins.
The files stay where they are; a passphrase is stored encrypted. Save checks the files, so a wrong passphrase or a key that doesn't belong to the certificate is caught there. The log shows which client certificate a request offered, and a failed handshake says why: an untrusted server certificate, a server that wants a client certificate, or one it refused.
Exported scripts don't take the app setting:
node my-flow.js --system-ca
node my-flow.js --ca company-ca.pem
CLEM_CERT_PASSPHRASE=… node my-flow.js --pfx client.pfx --cert-host api.bank.com
node my-flow.js --cert client.pem --key client.key
NODE_EXTRA_CA_CERTS works too.
A PFX exported the old way (RC2 or 3DES encryption, common from older Windows, Java keytool and OpenSSL 1) works in the app but not in exported scripts: Node.js 17 and later can't read it, and the script says so. Convert it once to PEM and pass that as both certificate and key:
openssl pkcs12 -legacy -in client.p12 -nodes -out client.pem
node my-flow.js --cert client.pem --key client.pemHTTP/2
Flow Settings → HTTP version picks the protocol of the flow's requests:
| Setting | Does |
|---|---|
| HTTP/1.1 (default) | What CLEM always used. |
| Auto | HTTP/2 when an https server offers it, HTTP/1.1 otherwise, as browsers and curl do. |
| HTTP/2 | Insists on it: a server that only speaks HTTP/1.1 fails the request, and an http:// URL is sent as HTTP/2 without TLS (h2c). |
A request can choose its own on its Request tab. In code, http({ url, httpVersion: "2" }) does the same, and response.httpVersion says what was used. The log shows "HTTP/2" next to the status (HTTP/2 has no status text).
The requests of a run share one HTTP/2 connection per server. Cookies, redirects, proxies, certificates, timeouts and Stop work as with HTTP/1.1. Exported scripts take --http-version.