Terminable middleware in Laravel - Step-by-Step Execution

Concept Flow - Terminable middleware

Request enters middleware

↓

Handle method runs

↓

Pass request to next middleware or app

↓

Response generated and sent back

↓

Terminable middleware's terminate method runs

↓

Cleanup or logging after response

↓

End

The middleware first handles the request, then after the response is sent, the terminate method runs for cleanup or logging.

Execution Sample

Laravel

class LogAfterResponse implements TerminableMiddleware {
  public function handle($request, Closure $next) {
    return $next($request);
  }
  public function terminate($request, $response) {
    // Log after response sent
  }
}

Middleware that passes the request through and logs after the response is sent.

Execution Table

Step	Action	Request State	Response State	Middleware Method	Effect
1	Request enters middleware	Received	None	handle	Middleware starts processing
2	handle calls next middleware/app	Passed along	None	handle	Request forwarded
3	Response generated by app	Processed	Generated	handle	Response ready to send
4	Response sent to client	Processed	Sent	handle	Client receives response
5	terminate method runs	Processed	Sent	terminate	Logs or cleanup after response
6	Middleware finishes	Processed	Sent	terminate	Middleware work complete

💡 terminate runs after response sent, then middleware completes

Variable Tracker

Variable	Start	After handle	After response	After terminate	Final
request	Incoming HTTP request	Passed to next	Processed by app	Available for terminate	No change
response	None	None	Created by app	Sent to client	No change

Key Moments - 2 Insights

Why does the terminate method run after the response is sent?

Because terminate is designed to run after the response is sent to allow tasks like logging or cleanup without delaying the user.

Can the terminate method modify the response sent to the client?

No, terminate runs after the response is sent, so it cannot change what the client receives, only perform post-response actions.

Visual Quiz - 3 Questions

Look at the execution table, at which step is the response sent to the client?

A Step 3

B Step 5

C Step 4

D Step 2

💡 Hint

Check the 'Effect' column for when the client receives the response.

According to variable_tracker, what is the state of the request during the terminate method?

A Incoming HTTP request

B Available for terminate

C Passed to next

D Processed by app

💡 Hint

Look at the 'After terminate' column for the request variable.

If the terminate method tried to modify the response, what would happen?

A The modification would be ignored because response is already sent

B The client would see the modified response

C The response would be delayed until terminate finishes

D An error would occur

💡 Hint

Refer to key_moments about when terminate runs relative to response sending.

Concept Snapshot

Terminable middleware in Laravel has two parts:
- handle method: processes request and passes it on
- terminate method: runs after response sent for cleanup or logging
Terminate cannot change the response sent to client.
Useful for tasks that should not delay user experience.

Full Transcript

Terminable middleware in Laravel works by first handling the incoming request in the handle method. This method passes the request to the next middleware or the application, which generates a response. After the response is sent to the client, the terminate method runs. This method is useful for tasks like logging or cleanup that should happen after the user receives the response. The terminate method cannot modify the response because it runs after sending. The execution flow starts with the request entering middleware, handle passing it on, response generation, response sending, then terminate running, and finally middleware finishing. Variables like request and response change state accordingly but remain accessible in terminate for post-response actions.