- Ctrl+D in the Single URL field runs a handshake probe against the typed endpoint. It detects HTTP and/or SOCKS5 without forwarding traffic or contacting external hosts. - HTTP-capable endpoints map to http://; SOCKS5-only endpoints map to socks5h://. Userinfo is preserved as typed. - Bare host:port input is accepted and defaults to http:// at save. - Update README privacy boundary and add .scratch/protocol-probe/spec.md.
1.7 KiB
Proxy Configuration
This context describes how one active proxy configuration is coordinated across independently switchable Linux configuration surfaces.
Language
Proxy Profile: A named, reusable set of proxy connection details and bypass rules. Avoid: Proxy, configuration preset
Active Profile: The Proxy Profile currently selected as the source for every Enabled Target; it may be absent when no Proxy Profiles exist. Avoid: Current proxy, selected preset
Target: A configuration surface that can independently receive proxy settings, such as the Shell environment, APT, or the Docker daemon. Avoid: Application, service
Available Target: A Target detected as applicable to the current system and therefore shown on the main switch panel. Avoid: Installed application, supported Target
Enabled Target: A Target whose actual configuration matches the Active Profile; a Target cannot be enabled when there is no Active Profile. Avoid: Active application, proxied app
Drifted Target: A Target whose managed configuration exists but no longer matches the Active Profile, whether because an update failed or an external change occurred. Avoid: Broken Target, partially enabled Target
External Target: A Target for which a recognized proxy configuration exists outside this tool's ownership; absence of detected external configuration is treated as Disabled. Avoid: Unknown Target, unmanaged error
Protocol Probe: A user-initiated handshake check against a Proxy Profile's endpoint that reports which proxy protocols (HTTP, SOCKS5) the endpoint speaks; it never forwards traffic through the proxy or contacts anything beyond the endpoint itself. Avoid: Connectivity test, latency check