HTTP method routing (GET, POST, PUT, DELETE) in Laravel - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of HTTP method routing in Laravel?

HTTP method routing in Laravel directs different types of HTTP requests (GET, POST, PUT, DELETE) to specific controller actions or closures. This helps the app respond correctly depending on the request type.

beginner

How do you define a route that responds only to GET requests in Laravel?

Use the Route::get() method. For example:
Route::get('/users', [UserController::class, 'index']);
This route only responds to GET requests to '/users'.

beginner

What Laravel method handles POST requests and when is it commonly used?

Route::post() handles POST requests. It is commonly used to submit data to the server, like form submissions or creating new resources.

intermediate

Explain how to define a route for updating a resource using PUT in Laravel.

Use Route::put() to define a route that handles PUT requests, which usually update existing data. Example:
Route::put('/users/{id}', [UserController::class, 'update']);
This updates the user with the given id.

intermediate

What is the use of Route::delete() in Laravel routing?

Route::delete() defines a route that listens for DELETE requests. It is used to remove or delete resources from the server. Example:
Route::delete('/users/{id}', [UserController::class, 'destroy']);

Which Laravel routing method handles form submissions that create new data?

A Route::get()

B Route::delete()

C Route::put()

D Route::post()

Route::post() is used for POST requests, which commonly handle form submissions to create new data.

What HTTP method does Route::put() in Laravel respond to?

A GET

B PUT

C POST

D DELETE

Route::put() responds to HTTP PUT requests, typically used to update existing resources.

Which route method would you use to delete a user resource in Laravel?

A Route::delete()

B Route::post()

C Route::put()

D Route::get()

Route::delete() listens for DELETE requests to remove resources.

If you want to show a list of users, which HTTP method and Laravel route would you use?

A POST and Route::post()

B DELETE and Route::delete()

C GET and Route::get()

D PUT and Route::put()

GET requests retrieve data, so Route::get() is used to show a list of users.

Which Laravel route method can handle multiple HTTP methods at once?

A Route::match()

B Route::get()

C Route::post()

D Route::delete()

Route::match() allows you to specify an array of HTTP methods to handle in one route.

Describe how Laravel routes handle different HTTP methods like GET, POST, PUT, and DELETE.

Think about how web browsers and forms send different types of requests.

Explain why using the correct HTTP method in Laravel routing is important for building web applications.

Consider how different actions on data should be separated.

Practice

1. Which HTTP method in Laravel routing is typically used to retrieve data from the server without changing it?

easy

A. GET

B. POST

C. PUT

D. DELETE

Solution

1. Step 1: Understand HTTP methods purpose

   GET requests are designed to fetch or read data without modifying it.

2. Step 2: Match method to Laravel routing

   In Laravel, routes defined with GET respond to data retrieval requests.

3. Final Answer:

   GET -> Option A

4. Quick Check:

   GET = Read data [OK]

Hint: GET is for reading data, no changes made [OK]

Common Mistakes:

• Confusing POST with GET for data retrieval
• Using PUT or DELETE for fetching data
• Thinking GET modifies data

2. Which of the following is the correct Laravel route definition for handling a POST request to '/submit'?

easy

A. Route::get('/submit', [FormController::class, 'store']);

B. Route::post('/submit', [FormController::class, 'store']);

C. Route::put('/submit', [FormController::class, 'store']);

D. Route::delete('/submit', [FormController::class, 'store']);

Solution

1. Step 1: Identify the HTTP method for creating data

   POST is used to send data to the server, typically for creating resources.

2. Step 2: Match Laravel route syntax for POST

   Route::post() defines a route that listens for POST requests.

3. Final Answer:

   Route::post('/submit', [FormController::class, 'store']); -> Option B

4. Quick Check:

   POST route syntax = Route::post('/submit', [FormController::class, 'store']); [OK]

Hint: Use Route::post() for form submissions [OK]

Common Mistakes:

• Using Route::get() for POST requests
• Mixing PUT or DELETE with form submission
• Incorrect method name in route definition

3. Given the following Laravel routes, what HTTP method should you use to update a user's profile?

Route::get('/user/{id}', [UserController::class, 'show']);
Route::post('/user', [UserController::class, 'store']);
Route::put('/user/{id}', [UserController::class, 'update']);
Route::delete('/user/{id}', [UserController::class, 'destroy']);

medium

A. PUT

B. GET

C. POST

D. DELETE

Solution

1. Step 1: Identify route for updating data

   The route with Route::put() is used for updating existing resources.

2. Step 2: Match HTTP method to update action

   PUT method is the standard for updating a resource like a user profile.

3. Final Answer:

   PUT -> Option A

4. Quick Check:

   Update = PUT method [OK]

Hint: PUT updates existing data, POST creates new [OK]

Common Mistakes:

• Using POST instead of PUT for updates
• Confusing GET with update actions
• Using DELETE to update data

4. You wrote this Laravel route to delete a post:

Route::post('/post/{id}', [PostController::class, 'destroy']);

Why might this cause a problem when trying to delete a post?

medium

A. The URL should not include an {id} parameter

B. Route syntax is incorrect for any HTTP method

C. The controller method name 'destroy' is invalid

D. POST method is not intended for deleting resources

Solution

1. Step 1: Understand HTTP methods for resource deletion

   DELETE method is the standard for deleting resources, not POST.

2. Step 2: Identify mismatch in route method

   Using Route::post() for deletion can cause unexpected behavior or conflicts.

3. Final Answer:

   POST method is not intended for deleting resources -> Option D

4. Quick Check:

   DELETE method needed for deletion [OK]

Hint: Use Route::delete() for deleting resources [OK]

Common Mistakes:

• Using POST instead of DELETE for deletions
• Ignoring HTTP method conventions
• Assuming controller method name causes error

5. You want to create a Laravel API that supports full CRUD operations on a 'product'. Which set of HTTP methods and routes correctly matches the standard RESTful pattern?

hard

A. Route::put('/product', [ProductController::class, 'index']);\nRoute::delete('/product', [ProductController::class, 'store']);\nRoute::get('/product/{id}', [ProductController::class, 'update']);\nRoute::post('/product/{id}', [ProductController::class, 'destroy']);

B. Route::post('/product', [ProductController::class, 'index']);\nRoute::get('/product', [ProductController::class, 'store']);\nRoute::delete('/product/{id}', [ProductController::class, 'update']);\nRoute::put('/product/{id}', [ProductController::class, 'destroy']);

C. Route::get('/product', [ProductController::class, 'index']);\nRoute::post('/product', [ProductController::class, 'store']);\nRoute::put('/product/{id}', [ProductController::class, 'update']);\nRoute::delete('/product/{id}', [ProductController::class, 'destroy']);

D. Route::delete('/product', [ProductController::class, 'index']);\nRoute::put('/product', [ProductController::class, 'store']);\nRoute::post('/product/{id}', [ProductController::class, 'update']);\nRoute::get('/product/{id}', [ProductController::class, 'destroy']);

Solution

1. Step 1: Match HTTP methods to CRUD actions

   GET for reading list (index), POST for creating (store), PUT for updating, DELETE for deleting.

2. Step 2: Verify route patterns and controller methods

   Routes in Route::get('/product', [ProductController::class, 'index']);\nRoute::post('/product', [ProductController::class, 'store']);\nRoute::put('/product/{id}', [ProductController::class, 'update']);\nRoute::delete('/product/{id}', [ProductController::class, 'destroy']); correctly pair HTTP methods with controller actions and URL patterns.

3. Final Answer:

   Route::get('/product', [ProductController::class, 'index']);\nRoute::post('/product', [ProductController::class, 'store']);\nRoute::put('/product/{id}', [ProductController::class, 'update']);\nRoute::delete('/product/{id}', [ProductController::class, 'destroy']); -> Option C

4. Quick Check:

   GET, POST, PUT, DELETE with correct methods = Route::get('/product', [ProductController::class, 'index']);\nRoute::post('/product', [ProductController::class, 'store']);\nRoute::put('/product/{id}', [ProductController::class, 'update']);\nRoute::delete('/product/{id}', [ProductController::class, 'destroy']); [OK]

Hint: Follow REST: GET-read, POST-create, PUT-update, DELETE-remove [OK]

Common Mistakes:

• Mixing HTTP methods and controller actions
• Incorrect URL patterns for resource IDs
• Using wrong methods for CRUD operations