Looking for some clarification on the following.
Documentation for Route via HTTP says:
The Read Timeout defines the maximum time (in milliseconds) allowed for response data (not necessarily the complete response) to be read for the outbound request. If exceeded, the routing will fail (or failover). To override the system default, clear the Use System Default] check box and enter a value. You may reference context variables.
My question is, when using round robin failover strategy with multiple backend servers does this mean that a request would be retried on the next server in the list on a read timeout? I would think the assertion would fail on a read timeout since a connection was established successfully and only failover on connection timeouts. Otherwise a request could be processed multiple times.