Will HTTP/1.1 429 Responses automatically send an Element into Timeout?
Below you can find the logic that is applied to timeout handling in terms of HTTP status codes ranges:
- 2XX: No timeout
- 3XX:
customRedirect enabled and the redirect is not properly handled: Timeout
customRedirect disabled and the redirect is properly handled: No Timeout - 4XX: Timeout
- 5XX: Timeout
As a result 429 Too Many Requests will automatically put the element in timeout if the last retry of the configured amount of retries on that connection still results in a 429 Too Many Requests or another one in the timeout range.
Hey Michael,
Not an expert on this matter, but based on this article, it will depend on the element timeout time and how the other HTTP sessions are answered.
The article describes a case where the element does not go into a timeout state, because the total time of not having responses is lower than the configured timeout time. If other request would keep on providing that same reply, the element would go in a timeout state.
So, at least from how I would understand, it depends on how many responses with HTTP/1.1 429 are returned in a row, i.e. if that exceeds the element timeout time.
That is correct, so similar to any other communication protocol in DataMiner. A timeout alarm is generated against the element timeout time that is set.
If I understand you correctly then, if you have 3 429’s returned in a 5 second time window, and then a 200OK returned 15 seconds later, if the device timeout is set to 30 seconds, then the element will not go into timeout at all?