retry on http 408 error ?

[Cactusbone]

Hi !
Depending on load, we might see some http 408 error (Request Time-out) and I think it's a good code to retry, since it means either the client was to slow to send the request, or the server was too busy to receive it.

What do you think ?

[FGRibreau]

If could make sense however I think we should consider it as a breaking change since it changes the default behaviour.

Not sure if we should support it out of the box or ask our users to leverage custom strategies

[Cactusbone]

Yeah, custom strategy would work. It's indeed a breaking change.
Should i change the PR to provide an alternative strategy so it's easy to use in place of current HTTPOrNetworkError ?

[FGRibreau]

@Cactusbone I think you should release it as an outside npm package and I will like it inside the README :)