ginuerzh 93bd2ea760 fix(hop): parenthesize host OR and normalize wildcard in filter->matcher rule ...

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.

2026-08-26 21:02:50 +08:00

..

cmd

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

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

loader

x: add generic cache component and HTTP response caching

2026-07-26 17:26:00 +08:00

parsing

fix(hop): parenthesize host OR and normalize wildcard in filter->matcher rule

2026-08-26 21:02:50 +08:00

config.go

fix(api): save config back to the loaded file path (gost/x#123)

2026-08-21 21:43:17 +08:00