Cookie handling in Laravel - Step-by-Step Execution

Concept Flow - Cookie handling

Start Request

↓

Check for Cookie

↓

Read Cookie

↓

Use Cookie

↓

Send Response

↓

End

This flow shows how Laravel checks for a cookie in a request, reads or creates it, then attaches it to the response before sending back to the browser.

Execution Sample

Laravel

<?php
// Set a cookie
return response('Hello')->cookie('user', 'Alice', 60);

// Get a cookie
$name = request()->cookie('user');

This code sets a cookie named 'user' with value 'Alice' for 60 minutes, then reads it from the request.

Execution Table

Step	Action	Cookie Present?	Cookie Value	Response Cookie Set	Output
1	Request arrives without 'user' cookie	No	null	No	No cookie read
2	Create response with cookie 'user'='Alice' for 60 minutes	No	null	Yes ('user'='Alice', 60 minutes)	Response ready with cookie
3	Send response to browser	No	null	Yes ('user'='Alice', 60 minutes)	Browser stores cookie
4	Next request arrives with 'user' cookie	Yes	Alice	No	Cookie read as 'Alice'
5	Use cookie value in app	Yes	Alice	No	App uses 'Alice' value
6	End of flow	-	-	-	-

💡 Flow ends after response sent and cookie read on next request

Variable Tracker

Variable	Start	After Step 2	After Step 4	Final
cookie_present	false	false	true	true
cookie_value	null	null	'Alice'	'Alice'
response_cookie_set	false	true	false	false

Key Moments - 2 Insights

Why does the cookie value appear null on the first request but 'Alice' on the next?

Because the cookie is set in the response and only sent back by the browser on the next request, as shown in steps 1-4 of the execution_table.

How does Laravel attach the cookie to the response?

Laravel uses the response()->cookie() method to add the cookie header before sending, as seen in step 2 where response_cookie_set becomes true.

Visual Quiz - 3 Questions

Look at the execution table, what is the cookie_value at step 1?

A undefined

B 'Alice'

C null

D empty string

💡 Hint

Check the 'Cookie Value' column at step 1 in the execution_table.

At which step does the response get the cookie attached?

A Step 1

B Step 2

C Step 4

D Step 5

💡 Hint

Look at the 'Response Cookie Set' column in the execution_table.

If the cookie expiration was changed to 120 minutes, which part of the execution_table would change?

A Response Cookie Set column

B Cookie Value column

C Cookie Present? column

D Output column

💡 Hint

Changing expiration affects how the cookie is set in the response, check 'Response Cookie Set' column.

Concept Snapshot

Laravel Cookie Handling:
- Use response()->cookie(name, value, minutes) to set a cookie.
- Use request()->cookie(name) to read a cookie.
- Cookies set in response arrive in next request.
- Cookie expiration is in minutes.
- Cookies help store small data on user browser.

Full Transcript

In Laravel, cookie handling starts when a request arrives. The app checks if the cookie exists. If not, it creates a cookie using response()->cookie() and sends it back. The browser stores this cookie and sends it on the next request. Then the app reads the cookie using request()->cookie(). This flow ensures data persists across requests. The cookie expiration time controls how long the browser keeps it. This step-by-step flow helps beginners see how cookies travel between browser and server in Laravel.