Skip to content

v0.5.1 — Proxy environment variables work without USE_SYSTEM_PROXY

Latest
Latest

Choose a tag to compare

View all tags
@galatanovidiu galatanovidiu released this 06 Oct 19:39
v0.5.1
ab25f45
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Proxy environment variables now work on their own. Before, SOCKS_PROXY, HTTPS_PROXY, ALL_PROXY and HTTP_PROXY were ignored unless USE_SYSTEM_PROXY=true was also set, so on a network that requires a proxy the connection timed out and the client saw no tools.

Upgrade notes

  • Proxy variables in your environment now apply. If HTTPS_PROXY or HTTP_PROXY is set in the environment that launches the proxy, for example for other tools, WordPress requests now go through that proxy as well. Add hosts to NO_PROXY to connect to them directly. (#133)
  • The token store is namespaced by package version, so upgrading to 0.5.1 requires users to authenticate again.

Fixed

  • SOCKS_PROXY, HTTPS_PROXY, ALL_PROXY and HTTP_PROXY route requests without USE_SYSTEM_PROXY. USE_SYSTEM_PROXY=true now only enables detection of the macOS system PAC file or SOCKS proxy, which is used when none of those variables is set. NO_PROXY works as before. (#133)

Documentation

  • The README documents the proxy variables and explains when to connect a client to WordPress directly instead of using the proxy. (#132, #133)

Full changelog: v0.5.0...v0.5.1

Assets 2
Loading