ginuerzhandgithub 0e0eab0c52 fix(cmd): restore unix socket port-forward semantics ...

Commit b3b5986 crammed the URL path into the listen/connect address and
disabled forward mode for path-based protocols, breaking the
`unix://a.sock/b.sock` (listen on a, forward to b) port-forward form and
producing an invalid `a.sockb.sock` address.

Distinguish the two URL forms by host presence:
- three-slash (unix:///abs.sock, empty host) → path is the absolute socket
  address, no forward target;
- two-slash (unix://a.sock/b.sock) → host is the socket and the path is a
  forward target (service) or ignored (node).

Add regression tests for both forms.

Co-Authored-By: Claude (claude-opus-4-8[1m])

2026-08-17 22:51:00 +08:00

..

cmd_test.go

fix(cmd): restore unix socket port-forward semantics

2026-08-17 22:51:00 +08:00

cmd.go

fix(cmd): restore unix socket port-forward semantics

2026-08-17 22:51:00 +08:00