HTTP Basics

By the Syncfusion DevTutorials team · Last updated October 20, 2026

Read every line of a real HTTP request and response: the method, path, query string, headers and JSON body, and why a missing Content-Type breaks a request.

HTTP (HyperText Transfer Protocol) is the set of rules that clients and servers use to communicate with each other over a network. Whenever an app requests data from a server or sends data to a server, it uses HTTP messages. Every API call is simply an HTTP request sent by a client and an HTTP response returned by a server. Learning HTTP helps you understand exactly how APIs work and makes it much easier to find and fix problems when something goes wrong.

Watch an App Fail

The Brew & Bytes app sends an order. The server rejects it. The app only shows "Something went wrong", so nobody knows the real reason. The example below sends the same order three different times. Press Run and look carefully at each response.

• The first request succeeds with 201 Created.
• The second request returns 415 Unsupported Media Type. The request does not include a Content-Type header, so the server does not know that the body contains JSON.
• The third request returns 400 Bad Request. The JSON data is incomplete and cannot be read correctly.

In simple words: the error information was already in the request and response messages. When you learn how to read those messages, you can quickly understand what went wrong instead of guessing.

TL;DR

• HTTP (HyperText Transfer Protocol) is the language used by clients and servers to communicate.
• A request contains a start line, headers, a blank line, and an optional body.
• A response contains a status line, headers, a blank line, and an optional body.
• A header provides extra information about the request or response.
• JSON is the most common data format used in API bodies.
• When something fails, read the request and response before changing any code.

A Real-World Example

Think about sending a parcel. The label tells where the parcel should go. Stickers provide extra instructions such as "Fragile" or "Handle with care". Inside the parcel is the actual item being sent. An HTTP message works in a similar way.

If a parcel does not have the correct handling instructions, the courier may not know how to treat it. Similarly, if a request does not include Content-Type, the server may not know how to process the body correctly.

What You Will Learn

In this lesson, you will learn:

1. The four parts of every HTTP request and response.
2. What methods, paths, and query strings are.
3. What headers do and why they are important.
4. How JSON is sent in the body of a request or response.
5. How to read an HTTP response manually.

The Request

Start Line, Headers, and Body

Every HTTP request starts with a single line called the start line.

The start line contains:

• The method
• The path

The method tells the server what action the client wants to perform.

For example:

• GET means "send me data".
• POST means "create something new".

The path tells the server which resource the client wants.

Examples:

/menu
/orders

The query string comes after a ? and provides extra information.

Example:

/orders?table=7

After the start line come the headers.

Each header contains:

Name: Value

Then there is a blank line. After the blank line comes the body, if the request includes one. The next example shows a server that simply returns information about the request it received. Press Run. Then try changing the path or adding a custom header such as:

X-Shop: MG Road

The response shows:

• The request method
• The path
• The query string
• The headers

X-App-Version is a custom header used by the application to tell the server which app version is making the request.

Common Headers

The Query String

Small pieces of information are usually sent in the query string. For example, a client may request only menu items priced at ₹150 or less.

The first request uses:

?maxPrice=150

Only the matching menu items are returned. The second request has no query string, so all menu items are returned. In C#, the parameter int? maxPrice is automatically filled from the query string. The ? indicates that the value is optional. In Hono, c.req.query("maxPrice") reads the same value.

The Response

Status Line, Headers, and Body

An HTTP response also follows a standard structure. It begins with a status line.

Example:

HTTP/1.1 200 OK

The status line contains:

• HTTP version
• Status code
• Status message

The status code tells the client what happened. After the status line come:

1. Headers
2. A blank line
3. The body

Servers can also add custom headers. The example below adds caching information and a custom header.

Notice these headers:

• Cache-Control
• X-Shop
• Content-Type

Content-Type is added automatically because the response body contains JSON. Headers beginning with X- are commonly used for custom information.

Read a Response by Hand

Before any library processes an HTTP response, it is simply text. The following example breaks a raw HTTP response into its individual parts.

The response contains:

1. A status line.
2. One or more headers.
3. A blank line.
4. A body.

When you understand these parts, debugging API problems becomes much easier.

JSON in the Body

JSON (JavaScript Object Notation) is the most common format used to send data in APIs.

JSON uses:

• { } for an object.
• [ ] for a list.
• Double quotes for text.
• Numbers without quotes.

Look again at the example near the top of this lesson.

The same JSON order was sent three times:

• With Content-Type: application/json and valid JSON, the order was created successfully.
• Without Content-Type, the server returned 415 Unsupported Media Type.
• With incomplete JSON, the server returned 400 Bad Request.

In ASP.NET Core, these checks happen automatically before your endpoint code runs. In Hono, you typically add these checks yourself.

Where You See This

• Browser Developer Tools: Open the Network tab to view requests and responses.
• HTTP Request Files: Visual Studio, Rider, and VS Code can send requests from .http files.
• Command Line Tools: Tools such as curl allow you to send requests and inspect raw HTTP responses.

Common mistakes

Exercises

What to Remember

• Every HTTP message has four parts: a start line, headers, a blank line, and a body.
• A request starts with a method and a path. A response starts with a status code.
• Headers carry extra information. Content-Type says what the body is.
• Small details go in the query string, after ?.
• When something fails, read the raw messages first.

Next: HTTP Methods. You will learn what GET, POST, PUT, PATCH and DELETE mean, and how to make a retry safe.