mirror of
https://github.com/go-gost/x.git
synced 2026-10-19 16:16:32 +00:00
ginuerzh
b2d901e70f
Add RESP protocol detection to the sniffing framework so plaintext Redis traffic on a port-reuse listener can be identified and routed by protocol. Sniff() now peeks 1 byte first to match RESP type bytes (*+-:$) without blocking, then falls through to the existing 5-byte TLS/HTTP/SSH detection. ParseRedisMetadata consumes exactly one RESP message via io.TeeReader and records command/key in HandlerRecorderObject.Redis. HandleRedis in both the sniffing (injected-dial) and forwarder (hop-selected) packages replays the captured first message and pipes the rest, so pipelined commands beyond the first are forwarded transparently. Wired into all 5 dispatch sites: sni, forward/local, forward/remote, http CONNECT, and relay tunnel handlers. forwarder paths route via resolveRedisNode using ProtocolSelectOption(ProtoRedis), enabling `protocol: redis` hop selection. Part of two-phase plan (2026-07-29-sniffing-redis-postgres.md); PostgreSQL deferred to phase 2.
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.