Download the PHP package poor-plebs/guzzle-retry-after-middleware without Composer
On this page you can find all versions of the php package poor-plebs/guzzle-retry-after-middleware. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download poor-plebs/guzzle-retry-after-middleware
More information about poor-plebs/guzzle-retry-after-middleware
Files in poor-plebs/guzzle-retry-after-middleware
Package guzzle-retry-after-middleware
Short Description A guzzle middleware to keep track of the Retry-After HTTP header and fail consecutive requests until this time has passed.
License MIT
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package guzzle-retry-after-middleware
poor-plebs/guzzle-retry-after-middleware
What is it for? | What are the requirements? | How to install it? | How to use it? | How to contribute?
A guzzle middleware to keep track of the Retry-After HTTP header and fail consecutive requests until this time has passed.
What is it for?
Some HTTP servers may respond with a Retry-After header, hinting the
client when to resume doing further requests to the server. The reasons can
differ in many ways, there is no strict case when to use that header. Most often
it is used together with the response status code 429 Too Many Requests doing
rate limiting or with 503 Service Unavailable when a dependency is offline or
the server is in maintenance. In both cases the server hints the client when to
retry the request to avoid preassure on the server that can not serve the
request at that point in time. In some cases, if the client will not respect
this back off request, the server may block or ban the client in some form.
To avoid that case, you can use this middleware that is specifically made for the guzzle http client. Following the documentation about middlewares, you can keep track of the retry after header's back off period so that requests during that period will fail with a dedicated exception before they are event sent out.
What are the requirements?
- PHP 8.0 or above
How to install it?
How to use it?
How to contribute?
poor-plebs/guzzle-retry-after-middleware follows semantic versioning. Read
more on semver.org.
Create issues to report problems or requests. Fork and create pull requests to propose solutions and ideas. Always add a CHANGELOG.md entry in the unreleased section.
All versions of guzzle-retry-after-middleware with dependencies
guzzlehttp/guzzle Version ^6.5.8 || ^7.4.5
guzzlehttp/promises Version ^1.0.0
nesbot/carbon Version ^2.62.1
psr/http-message Version ^1.0.0
psr/simple-cache Version ^1.0.0 || ^2.0.0 || ^3.0.0