Safe methods vs unsafe methods in Rest API - Visual Side-by-Side Comparison

Concept Flow - Safe methods vs unsafe methods

Client sends HTTP request

↓

Check HTTP method type

↓

Safe method?

↓

Read-only action

↓

Return data

↓

Response sent back to client

The client sends a request, the server checks if the HTTP method is safe (read-only) or unsafe (modifies data), then processes accordingly and sends a response.

Execution Sample

Rest API

GET /items
POST /items
GET /items/1
DELETE /items/1

Shows example HTTP requests using safe (GET) and unsafe (POST, DELETE) methods.

Execution Table

Step	HTTP Method	Request URL	Safe Method?	Action Taken	Response
1	GET	/items	Yes	Read list of items	200 OK with items list
2	POST	/items	No	Create new item	201 Created with item info
3	GET	/items/1	Yes	Read item details	200 OK with item details
4	DELETE	/items/1	No	Delete item	204 No Content
5	-	-	-	-	Stop: No more requests

💡 No more requests to process, execution ends.

Variable Tracker

Variable	Start	After 1	After 2	After 3	After 4	Final
items_list	[item1, item2]	[item1, item2]	[item1, item2, new_item]	[item1, item2, new_item]	[item2, new_item]	[item2, new_item]
last_response	None	200 OK with items list	201 Created with item info	200 OK with item details	204 No Content	204 No Content

Key Moments - 3 Insights

Why is GET considered safe even though it returns data?

GET is safe because it only reads data without changing anything on the server, as shown in steps 1 and 3 where data is returned but not modified.

Why are POST and DELETE unsafe methods?

POST and DELETE change the server data (creating or deleting items), shown in steps 2 and 4 where the items_list changes after these requests.

Can a safe method like GET ever modify data?

No, by definition safe methods do not modify data. The execution table shows GET requests only reading data without changes.

Visual Quiz - 3 Questions

Look at the execution table, what is the response after the POST /items request?

A 201 Created with item info

B 200 OK with items list

C 204 No Content

D 404 Not Found

💡 Hint

Check step 2 in the execution_table under the Response column.

At which step does the items_list get an item removed?

A Step 1

B Step 2

C Step 4

D Step 3

💡 Hint

Look at variable_tracker for items_list changes after each step.

If the GET method was changed to POST in step 3, what would happen?

A The server would read item details without changes

B The server would create a new item instead of reading

C The server would delete the item

D The server would return an error

💡 Hint

POST is an unsafe method that modifies data, unlike GET which is safe and read-only.

Concept Snapshot

Safe methods (like GET) only read data and do not change server state.
Unsafe methods (like POST, DELETE) modify data on the server.
Safe methods are idempotent and safe to repeat without side effects.
Unsafe methods can create, update, or delete resources.
Servers handle requests differently based on method safety.

Full Transcript

This visual execution shows how safe and unsafe HTTP methods work in REST APIs. The client sends requests with different methods. Safe methods like GET only read data and return it without changing anything. Unsafe methods like POST and DELETE modify the server data by creating or deleting items. The execution table traces each request step-by-step, showing the method, action, and response. The variable tracker shows how the list of items changes after unsafe methods. Key moments clarify why GET is safe and POST/DELETE are unsafe. The quiz tests understanding by asking about responses and data changes at specific steps. This helps beginners see clearly how safe and unsafe methods behave in real API calls.

Practice

1. Which HTTP method is considered safe because it only retrieves data without changing anything?

easy

A. DELETE

B. POST

C. PUT

D. GET

Solution

1. Step 1: Understand safe methods

   Safe methods do not change data on the server; they only read or retrieve data.

2. Step 2: Identify the safe method among options

   GET is the method used to request data without modifying it, making it safe.

3. Final Answer:

   GET -> Option D

4. Quick Check:

   Safe method = GET [OK]

Hint: Safe methods only read data, GET is the common safe method [OK]

Common Mistakes:

• Confusing POST as safe
• Thinking PUT is safe
• Assuming DELETE is safe

2. Which of the following is the correct syntax to send data to a server to create a new resource?

easy

A. POST /resource HTTP/1.1

B. GET /resource HTTP/1.1

C. DELETE /resource HTTP/1.1

D. PUT /resource HTTP/1.1

Solution

1. Step 1: Identify method for creating resources

   POST is used to send data to the server to create new resources.

2. Step 2: Check syntax correctness

   POST /resource HTTP/1.1 is the correct syntax to send data for creation.

3. Final Answer:

   POST /resource HTTP/1.1 -> Option A

4. Quick Check:

   Creating resource = POST [OK]

Hint: POST is for sending data to create, syntax includes POST and resource path [OK]

Common Mistakes:

• Using GET to send data
• Confusing DELETE with POST
• Using PUT for creation without context

3. What will be the result of this HTTP request method usage?

PUT /items/123 HTTP/1.1
Content-Type: application/json

{"name": "New Item"}

Choose the correct description.

medium

A. It retrieves the item with ID 123 without changes.

B. It updates or replaces the item with ID 123 with new data.

C. It deletes the item with ID 123 from the server.

D. It creates a new item without specifying an ID.

Solution

1. Step 1: Understand the PUT method purpose

   PUT is used to update or replace an existing resource at a specific URL.

2. Step 2: Analyze the request details

   The request targets /items/123 with JSON data, meaning it updates item 123.

3. Final Answer:

   It updates or replaces the item with ID 123 with new data. -> Option B

4. Quick Check:

   PUT updates resource = C [OK]

Hint: PUT replaces or updates resource at given URL [OK]

Common Mistakes:

• Thinking PUT retrieves data
• Confusing PUT with DELETE
• Assuming PUT creates without ID

4. Identify the error in this HTTP request if the goal is to safely retrieve data:

POST /users HTTP/1.1
Host: example.com

medium

A. The HTTP version is incorrect; it should be HTTP/2.0.

B. The Host header is missing, causing a syntax error.

C. POST is unsafe and changes data; GET should be used to retrieve data.

D. POST cannot be used with /users endpoint.

Solution

1. Step 1: Understand the goal and method used

   The goal is to safely retrieve data, but POST is used which changes data.

2. Step 2: Identify correct method for safe retrieval

   GET is the safe method to retrieve data without side effects.

3. Final Answer:

   POST is unsafe and changes data; GET should be used to retrieve data. -> Option C

4. Quick Check:

   Safe retrieval = GET, not POST [OK]

Hint: Use GET to retrieve data safely, not POST [OK]

Common Mistakes:

• Ignoring method safety
• Thinking Host header is missing
• Confusing HTTP versions

5. You want to design an API endpoint that allows clients to delete a user account safely. Which HTTP method should you use, and why?

hard

A. DELETE, because it explicitly removes the resource on the server.

B. POST, because it can send data and create resources.

C. GET, because it is safe and does not change data.

D. PUT, because it updates existing resources.

Solution

1. Step 1: Identify the action needed

   The goal is to remove (delete) a user account from the server.

2. Step 2: Choose the correct HTTP method for deletion

   DELETE is the method designed to remove resources safely and clearly.

3. Final Answer:

   DELETE, because it explicitly removes the resource on the server. -> Option A

4. Quick Check:

   Deleting resource = DELETE method [OK]

Hint: Use DELETE to remove resources explicitly and safely [OK]

Common Mistakes:

• Using GET for deletion
• Confusing POST with DELETE
• Using PUT instead of DELETE