[5.5] Throttles request - throw a 429 HTTP exception.

[lucasmichot]

Directly call throw a 429 HTTP Exception, so that :

• we let the exception handler return the response with a different content type
• we can decide to log or not this kind of exception

[taylorotwell]

Does an HTTP response still get passed back to previous middleware?

[lucasmichot]

If an exception is thrown here, of course the request lifecycle stops here.
So the next middleware are not executed (like for any other HTTP exceptions BTW, 404 and so on...)

[taylorotwell]

The previous middleware.

[lucasmichot]

Yes. For instance, if the previous middleware \Illuminate\Auth\Middleware\Authenticate comes just before and you cannot access this endpoint, this means that you will just have a \Illuminate\Auth\AuthenticationException (without X-RateLimit-* headers).

But if you are authenticated and pass \Illuminate\Auth\Middleware\Authenticate, then \Illuminate\Auth\AuthenticationException will handle the previous response, then the exception will be thrown.

The way it works is exactly as in \Illuminate\Auth\Middleware\Authenticate::authenticate