fix(mihomo): proxy the Google Play CN API

Assisted-by: DeepSeek Harness (gpt-6-astra)
This commit is contained in:
Ryan Yin committed 2026-11-10 08:31:35 +08:00
1 parent abda12c00a
commit 7c2f52c9d5
2 files changed
+13

No files matched your search

@@ -87,6 +87,16 @@ policy is opt-in: `rules_from:` (a decoded snapshot) or `file:` carry groups, ru
rule-providers over. The generator drops and reports malformed rules, misplaced `MATCH` and orphaned
targets instead of writing a config the core rejects.
## Google Play routing
`policy.yaml` routes `services.googleapis.cn` through `PROXY` on desktops and the gateway. This
addresses Google Play downloads stalling when direct API access selects a mainland CDN that is then
accessed through an overseas proxy.
References: [Google Play CDN report](https://blog.l3zc.com/2025/03/chinese-cdn-used-by-playstore/)
and
[Google Play domain classifications](https://github.com/v2fly/domain-list-community/blob/master/data/google-play).
## Gotchas
- `ipv6`, `dns.ipv6`, `fake-ip-range6`: the fake v6 pool is a lookup key, so the family the client
@@ -85,6 +85,9 @@ rules:
- GEOSITE,private,DIRECT
- GEOSITE,category-ads-all,REJECT
# Proxy the Play CN API to avoid mainland CDN selection for proxied downloads.
- DOMAIN,services.googleapis.cn,PROXY
# Steam picks its download caches from the IP it sees on the login (CM) connection:
# a proxied login downloads from Tokyo/SG/HK/LA. `cm.steampowered.com` must precede
# the `steampowered.com` catch, and both the Valve IP ranges below, which also serve