Entrypoint forwarding timeout override in Traefik Mesh changes upstream request deadline

Clarify how request lifecycle propagation is handled in Traefik Mesh when a client disconnects or a deadline expires, given that timeout behavior is governed by the underlying Traefik Proxy entrypoint and transport configuration.

The documented configuration transition occurs when operators override default forwarding timeouts at the mesh entrypoint level, which changes how long proxies wait for upstream responses before returning errors. SMI specifications do not natively express client cancellation or deadline propagation, so behavior relies on Traefik Proxy-level settings whose interaction with mesh routing is not fully documented. A compatibility boundary exists between SMI TrafficSplit policies and Traefik-native timeout settings, and the precedence that determines the effective deadline is not explicitly specified. Timeout defaults are version-sensitive to the bundled Traefik Proxy version.

Does Traefik Mesh propagate a downstream client disconnect to actively terminate the in-flight upstream request, or does the upstream request continue until the configured timeout expires? When an SMI TrafficSplit routes traffic to backends with differing Traefik timeout configurations, which configuration wins for the effective deadline? If a response timeout triggers a retry, is the original timed-out request cancelled or allowed to remain in the upstream connection pool?