Open danhermann opened 5 years ago
for anyone following here, this is caused by retry_non_idempotent
being a http client flag atm.
so a retry will be made by a client if creating the connection fails (e.g. with an io error or timeout).
retry_non_idempotent
does not apply for the plugin's retry mechanism. while its confusing to read a conf such as above and see the behavior - changing these are going to end up in breaking changes ...
With the following test config:
When
retryable_codes
are left at their default value that includes 500, HTTP 500 responses to POSTs are retried even thoughretry_non_idempotent
defaults to false.