Bird
Raised Fist0
Laravelframework~10 mins

Terminable middleware in Laravel - Interactive Code Practice

Choose your learning style10 modes available
Practice - 5 Tasks
Answer the questions below
1fill in blank
easy

Complete the code to define a terminable middleware class in Laravel.

Laravel
class LogAfterRequest {
    public function handle($request, Closure $next) {
        return $next($request);
    }

    public function [1]($request, $response) {
        // Code to run after response is sent
    }
}
Drag options to blanks, or click blank then click option'
AhandleAfter
BafterResponse
Cterminate
Dfinish
Attempts:
3 left
💡 Hint
Common Mistakes
Using 'handleAfter' or 'finish' instead of 'terminate'.
Not defining the terminate method at all.
2fill in blank
medium

Complete the code to register the terminable middleware in the HTTP kernel.

Laravel
protected $middleware = [
    // Other middleware
    [1]::class,
];
Drag options to blanks, or click blank then click option'
ALogAfterRequest
BTerminateMiddleware
CAfterResponseMiddleware
DTerminateRequest
Attempts:
3 left
💡 Hint
Common Mistakes
Using incorrect class names that don't exist.
Registering middleware in the wrong property like $routeMiddleware.
3fill in blank
hard

Fix the error in the terminable middleware method signature.

Laravel
public function [1](Request $request, Response $response) {
    // post-response logic
}
Drag options to blanks, or click blank then click option'
Afinish
Bhandle
CterminateRequest
Dterminate
Attempts:
3 left
💡 Hint
Common Mistakes
Using 'handle' instead of 'terminate'.
Using incorrect method names like 'finish'.
4fill in blank
hard

Fill both blanks to correctly call the next middleware and define the terminable method.

Laravel
public function handle($request, Closure $next) {
    return [1]($request);
}

public function [2]($request, $response) {
    // post-response logic
}
Drag options to blanks, or click blank then click option'
A$next
Bterminate
Chandle
Dfinish
Attempts:
3 left
💡 Hint
Common Mistakes
Using 'handle' instead of $next in the handle method.
Naming the terminable method incorrectly.
5fill in blank
hard

Fill all three blanks to create a terminable middleware that logs after response is sent.

Laravel
class LogAfterRequest {
    public function [1]($request, Closure $next) {
        return $next([2]);
    }

    public function [3]($request, $response) {
        // Log something here
    }
}
Drag options to blanks, or click blank then click option'
Ahandle
B$request
Cterminate
D$response
Attempts:
3 left
💡 Hint
Common Mistakes
Using wrong method names like 'finish' or 'handleAfter'.
Passing wrong variables to $next.

Practice

(1/5)
1. What is the main purpose of terminable middleware in Laravel?
easy
A. To validate user input before processing
B. To modify the HTTP request before it reaches the controller
C. To handle database migrations automatically
D. To run code after the HTTP response has been sent to the user

Solution

  1. Step 1: Understand middleware timing

    Terminable middleware runs after the response is sent, unlike regular middleware that runs before.
  2. Step 2: Identify terminable middleware purpose

    It is used for tasks like logging or cleanup after response delivery.
  3. Final Answer:

    To run code after the HTTP response has been sent to the user -> Option D
  4. Quick Check:

    Terminable middleware = post-response code [OK]
Hint: Terminable middleware runs after response is sent [OK]
Common Mistakes:
  • Confusing terminable middleware with regular middleware
  • Thinking it runs before the controller
  • Assuming it handles request validation
2. Which method must be implemented in a Laravel terminable middleware class?
easy
A. handle
B. process
C. terminate
D. finish

Solution

  1. Step 1: Recall terminable middleware interface

    Terminable middleware requires a terminate method to run code after response.
  2. Step 2: Differentiate from handle method

    handle runs before response, terminate runs after.
  3. Final Answer:

    terminate -> Option C
  4. Quick Check:

    Post-response method = terminate [OK]
Hint: Terminate method runs after response in terminable middleware [OK]
Common Mistakes:
  • Using handle instead of terminate for post-response code
  • Assuming process or finish are valid methods
  • Not implementing terminate method at all
3. Given this terminable middleware code, what will be logged after the response is sent?
class LogAfterResponse {
    public function handle($request, Closure $next) {
        return $next($request);
    }
    public function terminate($request, $response) {
        Log::info('Response sent with status: ' . $response->status());
    }
}
medium
A. Logs the request URL before sending the response
B. Logs the response status code after sending the response
C. Throws an error because terminate method is missing parameters
D. Does nothing because terminate is not called automatically

Solution

  1. Step 1: Analyze handle method

    The handle method passes the request to next middleware/controller without changes.
  2. Step 2: Analyze terminate method

    After response is sent, terminate logs the response status code using Log::info.
  3. Final Answer:

    Logs the response status code after sending the response -> Option B
  4. Quick Check:

    terminate logs status post-response [OK]
Hint: Terminate runs after response, so logs status then [OK]
Common Mistakes:
  • Thinking terminate runs before response
  • Assuming terminate is not called automatically
  • Confusing request and response parameters
4. Identify the error in this terminable middleware code:
class CleanupMiddleware {
    public function handle($request, Closure $next) {
        return $next($request);
    }
    public function terminate() {
        // cleanup code here
    }
}
medium
A. terminate method must accept $request and $response parameters
B. handle method must return a string, not a response
C. terminate method should be named handleTerminate
D. handle method must not call $next

Solution

  1. Step 1: Check terminate method signature

    Terminable middleware's terminate method must accept both $request and $response parameters.
  2. Step 2: Identify missing parameters

    The code's terminate method has no parameters, which will cause errors.
  3. Final Answer:

    terminate method must accept $request and $response parameters -> Option A
  4. Quick Check:

    terminate signature requires request and response [OK]
Hint: Terminate method needs both request and response parameters [OK]
Common Mistakes:
  • Omitting parameters in terminate method
  • Renaming terminate method incorrectly
  • Misunderstanding handle method return type
5. You want to log the total time taken to process a request including after the response is sent. How would you implement this using terminable middleware?
class RequestTimer {
    protected $startTime;

    public function handle($request, Closure $next) {
        $this->startTime = microtime(true);
        return $next($request);
    }

    public function terminate($request, $response) {
        // What code should go here?
    }
}
hard
A. $duration = microtime(true) - $this->startTime; \Log::info('Request took ' . $duration . ' seconds');
B. $duration = microtime(true) + $this->startTime; \Log::info('Request took ' . $duration . ' seconds');
C. return $this->startTime; // terminate must return a value
D. Call $this->handle($request, $next) again inside terminate

Solution

  1. Step 1: Calculate duration in terminate method

    Use current time minus stored start time to get total duration.
  2. Step 2: Log the duration

    Use Log::info to record the time taken after response is sent.
  3. Final Answer:

    $duration = microtime(true) - $this->startTime; \Log::info('Request took ' . $duration . ' seconds'); -> Option A
  4. Quick Check:

    Duration = now - startTime, then log [OK]
Hint: Subtract start time from current time in terminate to get duration [OK]
Common Mistakes:
  • Adding times instead of subtracting
  • Returning values from terminate method
  • Calling handle method inside terminate
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard