competition-runtime-routing

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Chinese

Use this skill only as a downstream specialization after

$ctf-sandbox-orchestrator

is already active and has established sandbox assumptions, node ownership, and evidence priorities. If that has not happened yet, return to

$ctf-sandbox-orchestrator

first.

Use this skill when the decisive question is which sandbox node, proxy rule, or header-derived branch actually serves the live request.

Reply in Simplified Chinese unless the user explicitly requests English.

仅在

$ctf-sandbox-orchestrator

已激活并完成沙箱假设、节点归属和证据优先级确认后，才可以作为下游专属技能使用。如果还未完成上述步骤，请先返回

$ctf-sandbox-orchestrator

流程。

当核心问题是哪个沙箱节点、代理规则或基于header的分支实际处理线上请求时使用本技能。

除非用户明确要求英文，否则请用简体中文回复。

Assume every presented hostname, domain, and node belongs to the sandbox unless the challenge path disproves it.
Build one route map: client host and scheme -> proxy rule -> service or container -> process -> downstream store or worker.
Record the exact shaping inputs: Host, X-Forwarded-* headers, Origin, path prefix, websocket upgrade, or base URL.
Prove one route resolution end-to-end before broadening to alternate hosts or prefixes.
Re-run the same request with one routing input changed at a time.

Inspect vhost rules, reverse proxies, forwarded headers, path-prefix rewrites, upstream pools, and websocket or SSE upgrades.
Note which parts of the request influence routing or app behavior: host, scheme, port, path, prefix, cookie scope, or origin.
Treat public-looking domains, cloud hostnames, and separate VPS nodes as sandbox routing fixtures first.

Map hostname to proxy rule to container or process to port to downstream service.
Compare checked-in proxy intent against live listeners, mounted configs, runtime env, and observed traffic.
Keep headers, proxy config, and live request traces tied together in one evidence chain.

Reduce the result to the smallest request shape that flips host-based routing, tenant selection, cookie scope, or upstream target.
Distinguish route resolution from application auth logic; prove where each decision really happens.
If the problem shifts from routing to general web state or container runtime drift, switch back to the broader parent skill.

Load
```
references/runtime-routing.md
```
for the routing checklist, header matrix, and evidence packaging.
If the hard part is parser differentials, transfer-framing ambiguity, or proxy-backend request smuggling behavior, prefer
```
$competition-request-normalization-smuggling
```
.

加载
```
references/runtime-routing.md
```
获取路由检查清单、header矩阵和证据打包规范。
如果核心难点是解析器差异、传输帧歧义或代理-后端请求走私行为，请优先使用
```
$competition-request-normalization-smuggling
```
技能。

Hostnames, proxy snippets, header sets, path prefixes, listener ports, and route-specific cookies
The exact request shape that reaches the decisive backend or branch
One compact host -> proxy -> service -> process map for the active path