Affects Version/s: None
Fix Version/s: 6.0.0
While trying to workaround
TS-3439 I decided to test out the connect retries option. During testing I found a case where it should not retry where it is.
The scenario is as follows:
- ATS makes a connection to an origin
- the origin acks the entire request
- the origin starts to send back a response (lets say first line of the header)
- the origin sends an RST
In this scenario ATS will re-connect to the origin, which is bad since we have already sent the request (and we aren't sure if the URL is re-entrant).