You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
Could a module parameter be added to retry a request n number of times in the event of a connection or server failure, without having to write a tedious bit of boiler plate config to catch failure response codes and retry.
A http(s) post or get is performed and the returned code is < 0 but > -20 (null url return code in libruxc) or is a 5xx or 6xx http error code. The module will reattempt the request up to the number of attempts defined in a module parameter.
By default this behaviour is disabled and would require explicitly defining the module parameter to enable it.
Requests could be exempted from automatic retries by either adding an additional argument to the function called in config, or a http header could be supplied X-RUXC-NORETRY for example using the existing function signature to exclude the request.
The header name could also be defined as a module parameter.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.