400 Bad Request in Rest API - Step-by-Step Execution

Concept Flow - 400 Bad Request

Client sends HTTP request

↓

Server receives request

↓

Server checks request syntax

↓

Process request

↓

Send response

↓

End

The server checks the client's request. If the request is malformed or invalid, it responds with 400 Bad Request and stops processing.

Execution Sample

Rest API

POST /api/data HTTP/1.1
Host: example.com
Content-Type: application/json

{"name": "John", "age": }

Client sends a POST request with invalid JSON (missing age value), causing a 400 Bad Request response.

Execution Table

Step	Action	Request Content	Validation Result	Server Response
1	Receive request	{"name": "John", "age": }	Syntax check started	None
2	Parse JSON body	{"name": "John", "age": }	Invalid JSON syntax	Prepare 400 Bad Request
3	Send response	N/A	N/A	HTTP 400 Bad Request with error message
4	End	N/A	N/A	Connection closed or waiting for new request

💡 Request JSON is invalid, so server stops processing and returns 400 Bad Request.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
request_content	N/A	{"name": "John", "age": }	{"name": "John", "age": }	N/A	N/A
validation_result	N/A	Pending	Invalid JSON syntax	N/A	N/A
server_response	N/A	None	Prepare 400 Bad Request	Sent 400 Bad Request	Completed

Key Moments - 3 Insights

Why does the server respond with 400 Bad Request instead of processing the data?

Because the request content is malformed (invalid JSON), the server detects this during syntax validation (see execution_table step 2) and stops further processing to avoid errors.

Is 400 Bad Request caused by server problems or client mistakes?

It is caused by client mistakes, such as sending malformed requests. The server is working correctly but refuses to process bad input (see execution_table steps 1-3).

What happens after the server sends the 400 Bad Request response?

The server ends the current request handling and waits for new requests or closes the connection (see execution_table step 4).

Visual Quiz - 3 Questions

Look at the execution_table, what is the validation result at step 2?

A Valid JSON

B Invalid JSON syntax

C Pending validation

D Server error

💡 Hint

Check the 'Validation Result' column at step 2 in the execution_table.

At which step does the server send the 400 Bad Request response?

A Step 3

B Step 2

C Step 1

D Step 4

💡 Hint

Look at the 'Server Response' column to find when the response is sent.

If the JSON was valid, how would the 'Validation Result' change at step 2?

A It would be 'Invalid JSON syntax'

B It would be 'Preparing 400 Bad Request'

C It would be 'Valid JSON'

D It would be 'Connection closed'

💡 Hint

Refer to the 'Validation Result' column in the execution_table and imagine a valid request.

Concept Snapshot

400 Bad Request:
- Means client sent a malformed or invalid request
- Server checks request syntax before processing
- If invalid, server responds with HTTP 400 status
- Client must fix request format to succeed
- Common causes: bad JSON, missing fields, wrong headers

Full Transcript

When a client sends an HTTP request, the server first checks if the request is valid. If the request has bad syntax, like invalid JSON, the server stops processing and sends back a 400 Bad Request response. This tells the client that the request was wrong and needs fixing. The server does not process bad requests to avoid errors. After sending the 400 response, the server ends the current request handling and waits for new requests. This error is caused by client mistakes, not server problems.