I believe the first peer in the list is the leader at the time the list was retrieved. This means that for STRONG_CONSISTENCY requests that just need to be retried due to a network glitch (not a loss of leader), they will retry with a peer and be redirected back to the first value. This is different from today - the first retry would go to the leader and, assuming the network glitch was temporary, the request will succeed without a redirect.

I just want to make sure this change in behavior is intentional.