How to solve the problem of laravel throttle middleware failure

This article mainly introduces Laravel's throttle middleware failure Problem solving method, briefly analyzes the reasons of throttle middleware failure problem and puts forward the solution, which has certain reference value, the need of friends can refer to

In this paper, the solution of Laravel throttle middleware failure problem is described. Share to everyone for your reference, as follows:

According to the official explanation, access frequency limits are simple:

Route::get (' Test ', function () {  return ' Helle World ';}) ->middleware (' throttle ');

It is also true that the cache stores access times and makes judgments.

Previously, Zizaco/entrust (a role-based rights Management Pack) was used, in which the cache_driver=file in. Env was changed to Cache_driver=array. So the problem arises. The laravel supports a variety of cache drivers, file, Array, Db, Redis, and so on, but throttle seems to work with a file type of driver.

My changes are as follows:

vendor/illuminate/cache/ratelimiter.php file

Public function __construct (Cache $cache) {    $this->cache = $cache;} Public Function __construct () {    $this->cache = App (' Cache ')->driver (' file ');}

Change the top to the following. The throttle middleware also works.

The above is the whole content of this article, I hope that everyone's learning has helped, more relevant content please pay attention to topic.alibabacloud.com!