Request headers (Content-Type, Accept) in Rest API - Step-by-Step Execution

Concept Flow - Request headers (Content-Type, Accept)

Client prepares request

↓

Set headers: Content-Type, Accept

↓

Send request to server

↓

Server reads Content-Type

↓

Server processes data accordingly

↓

Server prepares response

↓

Server sets response Content-Type

↓

Client reads response based on Accept header

The client sets Content-Type to tell the server the data format sent, and Accept to tell what response formats it can handle. The server uses these headers to process and respond correctly.

Execution Sample

Rest API

POST /api/data HTTP/1.1
Content-Type: application/json
Accept: application/xml

{"name":"Alice"}

Client sends a POST request with JSON data and asks for XML response.

Execution Table

Step	Action	Header Checked/Set	Value	Effect
1	Client prepares request	Content-Type	application/json	Tells server data is JSON
2	Client prepares request	Accept	application/xml	Tells server client wants XML response
3	Client sends request	-	-	Request sent with headers and body
4	Server receives request	Content-Type	application/json	Server knows to parse JSON body
5	Server processes data	-	-	Server reads JSON data {"name":"Alice"}
6	Server prepares response	Content-Type	application/xml	Server sets response format to XML
7	Server sends response	-	-	Response sent in XML format
8	Client receives response	Accept	application/xml	Client reads XML response as requested
9	End	-	-	Request-response cycle complete

💡 Request-response cycle ends after client receives response matching Accept header

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 4	After Step 6	Final
Content-Type	none	application/json	application/json	application/json	application/xml	application/xml
Accept	none	none	application/xml	application/xml	application/xml	application/xml
Request Body	empty	empty	{"name":"Alice"}	{"name":"Alice"}	{"name":"Alice"}	{"name":"Alice"}
Response Body	empty	empty	empty	empty	<name>Alice</name>	<name>Alice</name>

Key Moments - 3 Insights

Why do we set Content-Type in the request?

Content-Type tells the server what format the data in the request body is, so the server knows how to read it. See execution_table step 4.

What does the Accept header do?

Accept tells the server what response formats the client can handle. The server uses this to decide the response format. See execution_table steps 2 and 6.

Can the server ignore the Accept header?

Yes, but usually it tries to honor it. If it can't provide the requested format, it may respond with an error or default format. This is implied in step 6.

Visual Quiz - 3 Questions

Look at the execution_table, what is the Content-Type header value when the server processes the request?

A application/json

B text/plain

C application/xml

D none

💡 Hint

Check step 4 in the execution_table where the server reads Content-Type

At which step does the client specify it wants an XML response?

A Step 1

B Step 3

C Step 2

D Step 6

💡 Hint

Look at when Accept header is set in the execution_table

If the client changed Accept to application/json, what would likely change in the execution_table?

A Client would send JSON body at step 1

B Server would set response Content-Type to application/json at step 6

C Server would ignore Content-Type header

D No change in response format

💡 Hint

Refer to step 6 where server sets response Content-Type based on Accept header

Concept Snapshot

Request headers Content-Type and Accept:
- Content-Type: tells server the format of data sent (e.g., application/json)
- Accept: tells server what response formats client can handle (e.g., application/xml)
- Server uses Content-Type to parse request body
- Server uses Accept to format response
- Proper headers ensure smooth data exchange in APIs

Full Transcript

In REST API communication, the client sends headers to tell the server about the data format. Content-Type header specifies the format of the data sent in the request body, such as JSON or XML. The Accept header tells the server what response formats the client can understand. The server reads Content-Type to parse the incoming data correctly and uses Accept to decide the response format. This exchange ensures both sides understand each other and data is processed properly. The execution steps show the client setting these headers, the server reading them, processing data, and responding accordingly.