The gateway token refresh request now routes through an httpsAgent built from the configured HTTP proxy and no longer follows redirects (maxRedirects: 0). It also classifies specific transient failure reasons.
Gateway TLS refresh now proxies through configured HTTP proxy and follows no redirects
Gateway token refresh now goes through the configured HTTP proxy and follows no redirects.
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
AuthArea: what it touches
Internal ChangesKind: in v2.1.257,
Internal ChangesSection of the release