952622a965
When a registration response from cloudflared gets lost on it's way back to the edge, the edge service will retry and send another registration request. Since cloudflared already has bound the local UDP socket for the provided request id, we want to re-send the registration response. There are three types of retries that the edge will send: 1. A retry from the same QUIC connection index; cloudflared will just respond back with a registration response and reset the idle timer for the session. 2. A retry from a different QUIC connection index; cloudflared will need to migrate the current session connection to this new QUIC connection and reset the idle timer for the session. 3. A retry to a different cloudflared connector; cloudflared will eventually time the session out since no further packets will arrive to the session at the original connector. Closes TUN-8709 |
||
|---|---|---|
| .. | ||
| v3 | ||
| constants.go | ||
| conversion.go | ||
| datagram.go | ||
| datagram_test.go | ||
| datagramv2.go | ||
| metrics.go | ||
| param_unix.go | ||
| param_windows.go | ||
| safe_stream.go | ||
| safe_stream_test.go | ||
| tracing.go | ||