[KongchangAI]
Concept

route.reason

A metadata field returned by a proxy service that explains the exit routing decision actually applied to a request, typically including fields such as country, city and network_type.

Timeline (last 90 days)

Oct 28

The route.reason field in proxy responses (which contains information such as the actual egress country and city) should be logged as an egress receipt to facilitate tracing and verifying the actual egress location.

Unverified50%
Oct 28

route.reason is metadata returned by the proxy service, typically containing fields such as country, city, and network_type, and sometimes also a reason code indicating the reason for a routing fallback (such as falling back to a country egress when the target city is unavailable).

Unverified50%
Oct 28

If route.reason is not logged, then when the proxy is misconfigured or routing falls back, the agent may unknowingly obtain content for the wrong region, leading to data bias.

Unverified50%
Oct 28

One-stop configuration scheme: match country, city, and language, adapt the network type to the strictness of the site, assign a session name to the flow, and store route.reason for auditing; these settings apply across tasks in different regions.

Unverified50%

All Facts (4)

Source Articles