Okhttp: OKHttp retry

[jeffreyfan8]

When OKHTTP retries because of a 408, it does not respect the "Retry-After" header. It looks like this is a standard header. Could we add in this feature to respect the "Retry-After" header when retrying.

Thanks.

[JakeWharton]

I would think if this value is non-zero we should be returning the response
directly and push the work of deciding to retry onto the application layer.

On Wed, Oct 25, 2017 at 12:42 AM jeffreyfan8 [e-mail]
wrote:

When OKHTTP retries because of a 408, it does not respect the
"Retry-After" header. It looks like this is a standard header. Could we add
in this feature to respect the "Retry-After" header when retrying.

Thanks.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/square/okhttp/issues/3665, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAEEEbS_yie8cl1P2QPk09eIwvgk8V8lks5svoPbgaJpZM4QFSF5
.

[yschimke]

n.b. not clear that 408 with Retry-After is an official or common thing, but seems implicit.