You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
if not set, which is the default, the retry delay is determined by the value of the Retry-After header on HTTP 429/503 responses. If the header is not set, the default delay follows a simple exponential backoff: 1s, 2s, 4s, 8s, ...
"expected :retry_delay function to return non-negative integer, got: #{inspect(other)}"
end
end
end
I'm unsure if this is a bug and it should always use the :retry_after option if it's set, or if it's a documentation fix to clarify that :retry_after is ignored when there's a Retry-After header.
The text was updated successfully, but these errors were encountered:
The documentation for
:retry_delay
says:This makes it seem like the priority would be:
:retry_delay
optionBut it seems that it's really:
:retry_delay
optionreq/lib/req/steps.ex
Lines 2210 to 2238 in ba4de2a
I'm unsure if this is a bug and it should always use the
:retry_after
option if it's set, or if it's a documentation fix to clarify that:retry_after
is ignored when there's a Retry-After header.The text was updated successfully, but these errors were encountered: