v4.5.2
Deprecation
Starting from this v4.5.2 release, the parsing of non-standard retry-after
header values returned by some non-standard compliant servers is deprecated.
It still works, for now, but will return a deprecation error message even if the status of the link is alive
.
Behaviour starting at version 4.7.0
This library will not support non-standard 'retry-after' header values after its 4.7.0 version.
Starting with version 4.7.0, non standard retry-after
header values (for instance 1m30s
instead of 90
value in seconds) will be ignored and handled like there's no header returned. A default 60 seconds retry delay will apply.
This default delay is overridable using the fallbackRetryDelayInMs
parameter.
The deprecation warning message will be removed.
Change log
- #22 Add support for retry count on 429 response codes (@andreizet)
- #25 fixes 429 "Too Many Requests" retries that don't follow standard (@NicolasMassart)
See CHANGELOG.md for complete list of changes over versions.