mirror of
https://github.com/go-gost/x.git
synced 2026-10-19 16:16:32 +00:00
ginuerzh
93bd2ea760
filterToMatcherRule produced `Host(x) || Host(.x) && Proto(...) && ...`, but the matcher DSL (vulcand/predicate) binds && tighter than ||, so the apex Host(x) branch bypassed the protocol/path conjuncts — a request to the apex with a non-matching protocol/path matched where the legacy filter (AND of host/protocol/path) rejected it. Also normalize `*.example.com` to `.example.com` before the leading-dot branch: legacy ParseNode did this so both forms matched apex+subdomains; without it, `*.example.com` reached Host() as a wildcard matching only subdomains, dropping apex coverage that `.example.com` still had. - Parenthesize the host OR when protocol/path conjuncts follow. - Strip leading `*` + ensure leading dot, mirroring legacy normalization. - Update TestFilterToMatcherRule expectations; add dot/star combined cases. - Add TestFilterToMatcherRule_Precedence: runtime guard that apex+wrong proto/path is rejected and apex/subdomain+valid is accepted, for both `.example.com` and `*.example.com` forms.
x
The implementation layer for the GOST proxy framework. Every interface defined in core/ is implemented here — handlers, listeners, dialers, connectors, plus config parsing, registries, and all cross-cutting concerns.
Package layout
| Directory | Purpose |
|---|---|
handler/ |
Protocol handlers (http, socks4/5, ss, ssh, tunnel, tun, dns, redirect, etc.) |
listener/ |
Protocol listeners (tcp, tls, ws, http2/3, quic, kcp, icmp, tun, udp, etc.) |
dialer/ |
Outbound dialers (tcp, tls, ws, http2/3, quic, grpc, ssh, wg, kcp, icmp, etc.) |
connector/ |
Destination connectors (http, socks4/5, ss, ssh, relay, tunnel, direct, etc.) |
config/ |
Config struct, YAML/JSON parsing, and service construction |
registry/ |
Typed global registries for all component types |
service/ |
Accept loop wiring listener + handler |
chain/ |
Multi-hop forwarding chain and route implementation |
router/ |
Route table router (destination-based routing) |
hop/ |
Node group with load-balanced selection |
selector/ |
Load-balancing strategies (round-robin, random, weighted, hash) |
auth/, bypass/, admission/ |
Authentication, bypass rules, admission control |
resolver/, hosts/ |
DNS resolution and host mapping |
limiter/ |
Traffic, connection, and rate limiters |
recorder/, observer/ |
Traffic recording and observability |
ingress/, sd/, routing/ |
Ingress control, service discovery, routing rules |
logger/, metrics/, api/ |
Logging, Prometheus metrics, Web API |
metadata/, ctx/ |
Metadata key-value system and context propagation |
internal/ |
Shared internals — not importable externally |
Component pattern
Every handler, listener, dialer, and connector follows the same pattern: init() registers a constructor into a global registry, the constructor takes functional options, and Init(metadata.Metadata) extracts typed configuration from the metadata key-value map.
See CLAUDE.md for detailed architecture and conventions.