TortoiseSVN’s Proxy Groups Match Hosts, Not Repository Paths

TortoiseSVN uses Subversion’s runtime configuration for server-specific proxy settings. On Windows, edit the applicable servers file under %APPDATA%\Subversion and add a named group:

[groups]
external = svn.partner.example, *.vendor.example

[external]
http-proxy-host = proxy.example.net
http-proxy-port = 8080

Merge those sections into the existing file. The group value is a list of hostname patterns; the matching section supplies the connection settings for those hosts. For a public repository route, a host and port from the HTTP proxy list can fill that section’s endpoint fields.

This works when the repositories needing a proxy are distinguishable by hostname. It is not a rule for arbitrary repository paths such as /repo-a versus /repo-b on the same server.

Preserve existing global settings and proxy exceptions when reviewing the effective result. A host grouping changes how Subversion reaches the server; it does not change that repository’s own authentication.

Use the matching http-proxy-username and http-proxy-password settings only when the intermediary requires them, with the configuration protected appropriately for those credentials.