Question 98463 in Nginx Question posted in
The official documentation can be found here.

Laravel testing – 429 Too Many Requests – Nginx

As I move forward in my Laravel project I have several tests for controllers and now I’m facing with this issue.

Some of my tests are failing with this message:

Expected response status code [200] but received 429.
Failed asserting that 200 is identical to 429.

I tried to solve with these methods:

  1. Add withoutMiddleware() to TestCase.php:
public function setUp(): void
{
    parent::setUp();

    $this->withoutMiddleware(
        ThrottleRequests::class
    );
}
  1. Add REQUESTS_PER_MINUTE to phpunit.xml:
<phpunit>
  <php>
    ...
    <server name="REQUESTS_PER_MINUTE" value="500"/>
  </php>
</phpunit>
  1. Change my dockerized nginx config for this:
server {
    location ~ .php$ {
        limit_req zone=one burst=5;
    }
}
limit_req_zone  $binary_remote_addr  zone=one:10m   rate=100r/s;

Neither solution helped.

I don’t want to change the Laravel’s throttle settings only because of testing. I think here need to be a valid solution for this without changing the framework’s settings.

Any suggestion how can I solve this issue?

Tags:

3

Answers


  1. 0

    My solution to this, although not the most elegant was to replace the ThrottleMiddleware with my own and checking the env for testing, effectively disabling laravel’s throttling for for phpunit. :

    <?php

namespace AppHttpMiddleware;

use IlluminateRoutingMiddlewareThrottleRequestsWithRedis;
use Closure;

class ThrottleRequests extends ThrottleRequestsWithRedis
{
    public function handle($request, Closure $next, $maxAttempts = 60, $decayMinutes = 1, $prefix = '')
    {
        if (config('app.env') === 'testing') {
            return $next($request);
        }

        return parent::handle($request, $next, $maxAttempts, $decayMinutes, $prefix);
    }
}

    You will then need to update your kernel.php to use your new class e.g.

    protected $routeMiddleware = [
...
'throttle' => AppHttpMiddlewareThrottleRequests::class,
...
];
    Login or Signup to reply.
  2. 0

    Frank’s solution works but makes not possible to use named limiters. Code below passes correct arguments list and allow to detect named limiters

    <?php

namespace AppHttpMiddleware;

use Closure;
use IlluminateRoutingMiddlewareThrottleRequestsWithRedis;

class ThrottleRequests extends ThrottleRequestsWithRedis
{
    public function handle($request, Closure $next, $maxAttempts = 60, $decayMinutes = 1, $prefix = '')
    {
        if (app()->environment('production')) {
            return parent::handle(...func_get_args());
        }

        return $next($request);
    }
}
    Login or Signup to reply.
  3. 0

    I was currently facing this same issue testing with Laravel 9.

    I solved it adding inside the ‘configureRateLimiting()’ method in ‘RouteServiceProvider.php’ the following code:

    RateLimiter::for('test', function (Request $request) {
    return Limit::perMinute(XX)->by($request->ip());
});

    Replace the ‘XX’ with the max amount of API requests per minute you want to allow during testing.

    After that run:

    php artisan config:clear

    And:

    php artisan cache:clear

    I hope this helps!

    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search