Which Proxy Wins in Git LFS 3.7.0?

Follow environment selection, nonempty URL-matched Git overrides and bypass rules for the actual LFS request URL.

A nonempty Git http.proxy value matching the request URL overrides the environment-derived proxy in Git LFS 3.7.0. An empty Git value does not clear that environment route.

For this release, follow selection in this order:

  1. Read HTTPS_PROXY and HTTP_PROXY. A nonempty lowercase https_proxy or http_proxy replaces its corresponding uppercase value.
  2. For HTTPS, prefer the HTTPS candidate and use the HTTP candidate as fallback.
  3. Apply a matching nonempty Git http.proxy value in place of those candidates.
  4. Apply bypass rules to the chosen request URL. A nonempty no_proxy replaces NO_PROXY.

If the intention is direct access, inspect inherited inputs and the intended bypass instead of assuming an empty Git entry erased them.

Use the actual LFS URL for the comparison. API and object destinations may differ from the Git remote, changing which URL-scoped setting matches.

Keep the installed LFS version with the diagnosis. LFS uses its own Go HTTP transport; precedence from Git's libcurl path does not explain this selection code.

འབྲེལ་བའི་རྩོམ་ཡིག