[jsonbailey]

fix: Prevent special characters in the events URI or temp file path from breaking event delivery on Windows

Summary

Adds an http_proxy client option that sends all SDK requests to LaunchDarkly through a web proxy. The value is a proxy URL, for example http://my-proxy:8080 or http://user:pass@my-proxy:8080. This matches the proxy option in the Python and Go SDKs.

• The Guzzle feature requester, the Guzzle event publisher, and the default curl event publisher all use the option. Guzzle gets it as its proxy request option, and the curl publisher passes --proxy to curl.
• The proxy is used for both HTTP and HTTPS targets.
• The option overrides the HTTPS_PROXY and HTTP_PROXY environment variables for SDK connections. The NO_PROXY environment variable still applies, because curl reads it. If the option is not set, the environment variables apply as before.
• On Windows, the curl publisher uses PowerShell Invoke-WebRequest -Proxy, which does not read credentials from the proxy URL. For a proxy that requires authentication on Windows, use Guzzle::eventPublisher(). The Curl docblock documents this.
• An http_proxy value that is not a non-empty string is ignored with a warning, and the environment variables apply.

---

Note

Overview
Adds a new http_proxy client configuration option so LaunchDarkly HTTP traffic can be sent through an explicit proxy URL (aligned with other LaunchDarkly SDKs).

Util::httpProxy() centralizes parsing: only non-empty strings are honored; invalid values are logged and ignored so default proxy environment behavior is unchanged when the option is absent or bad.

The Guzzle feature requester and event publisher pass the URL as Guzzle’s proxy option. The default curl event publisher adds --proxy on Unix and Invoke-WebRequest -Proxy on Windows. Docs on LDClient and the integration factories describe precedence over HTTP_PROXY/HTTPS_PROXY for SDK calls only, plus the Windows PowerShell credential limitation.

Curl event publisher also tightens PowerShell quoting for payload file paths and URIs. Tests cover curl argument wiring and integration paths that only succeed when traffic goes through a local proxy.

^{Reviewed by Cursor Bugbot for commit 3f6f862. Bugbot is set up for automated code reviews on this repo. Configure here.}

[kinyoklion]

The option has priority over the proxy environment variables, such as HTTPS_PROXY, for SDK connections only. If the option is not set, behavior does not change and the environment variables still apply.

This doesn't appear to be accurate. CURL reads the proxy environment variables directly and no_proxy overrides the manually specified proxy configuration.

[jsonbailey]

This doesn't appear to be accurate. CURL reads the proxy environment variables directly and no_proxy overrides the manually specified proxy configuration.

It was fixed in the code docs but not in the PR description. I've updated it.