docs: клиентский профиль маршрутизации HAPP и его переопределение - #21
Open
tony-adamson wants to merge 1 commit into
Open
docs: клиентский профиль маршрутизации HAPP и его переопределение#21tony-adamson wants to merge 1 commit into
tony-adamson wants to merge 1 commit into
Conversation
The subscription endpoint ships a client-side routing profile in the routing: response header, and the managed default tunnels everything. The override file that changes it was mentioned in one line of the architecture docs, without a schema, an example, or the difference from server-side bypass routing. Bypass routing only changes where the server sends a request; the client still tunnels it, so a Russian site keeps seeing the VPS address. On a node without a cascade the catch-all outbound is already direct, so bypass cannot help there. Split routing is only reachable through the client profile, which made this the most common thing operators had to rediscover on their own. Adds a Configuration section in en/ru/zh-CN covering the two environment variables, GlobalProxy semantics, a complete split-tunnel example, and the three mistakes that are easy to make: Telegram matching by IP rather than domain, LastUpdated needing to grow, and geo database URLs being per-subscriber. Co-Authored-By: Claude Opus 5 <[email protected]> Claude-Session: https://claude.ai/code/session_0121QZ51XSKaiKcRrtoVQTDg
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Проблема
Подписка отдаёт клиенту HAPP профиль маршрутизации в заголовке
routing:, и управляемый профиль поумолчанию заворачивает в туннель всё, кроме приватных диапазонов IPv4. Дефолт разумный, но у него
есть следствие, с которым сталкивается почти каждый, кто ставит Xrayebator под Россию: Ozon, банки,
Госуслуги и ВК видят зарубежный адрес VPS и отвечают заглушкой.
Механизм, который это меняет, —
.happ_routing.json— упомянут в документации ровно одной строкой вописании архитектуры: без схемы, без примера и без объяснения, чем он отличается от серверного
Bypass routing. Разбираться пришлось по коду
subhttp.sh.Что в PR
Раздел «Профиль маршрутизации клиента HAPP» в
docs/configuration.mdи переводы вdocs/ru/иdocs/zh-CN/:сервер, а клиент всё равно заворачивает его в туннель, поэтому адресат видит адрес VPS; на
ноде без каскада общий outbound и так
direct, и bypass там не меняет ничего;HAPP_ROUTING_ENABLEDиHAPP_ROUTING_JSON_FILE;GlobalProxyв обе стороны;надо брать с core.telegram.org, а не по памяти;
LastUpdatedобязан расти, иначе HAPP непереимпортирует профиль; ссылки на geo-базы привязаны к подписчику.
Только документация, код не тронут.
🤖 Generated with Claude Code
https://claude.ai/code/session_0121QZ51XSKaiKcRrtoVQTDg