Understanding HTTP Request and Response: A Study Note

Today I am pleased to share my study notes on HTTP protocol request and response.

If any definition is unclear, click it to see the documentation description.

Or you can search the content on Baidu to see its meaning.

Request parameters

What are request parameters? They may not always be present; if they exist they are displayed, otherwise not.

Other details can be viewed at: http://www.jikexueyuan.com/course/1706.html

HTTP consists of two parts: request and response.

1. Let's look at the request content:

Header:

Body content:

GET requests have no Body; only POST requests have a Body.

Next, let's look at the response details:

Status line content:

Unsuccessful requests start with 4xx or 5xx; 4xx usually indicates client-side request issues, 5xx indicates server response problems. Request errors may be due to user input mistakes, not necessarily bugs, while server response errors are generally bugs.

Headers similar to those in the request.

Not all responses have a body; for example, 201 and 204 do not.

Feedback information at the top right:

Have Fun ~ Tester ！

FunTester testing framework overview

10万QPS, K6, Gatling and FunTester ultimate showdown

Single-machine 120k QPS – FunTester revenge

Over ten thousand words reviewing FunTester's history

Automated testing in production environments

Tips for writing test cases

Seven skills to become an automated testing expert

IoT testing

Why testing misses bugs

Selenium automation best practices (Part 1)

Selenium automation best practices (Part 2)

Selenium automation best practices (Part 3)

Socket interface asynchronous verification practice

Selenium 4 and beyond: APIs you may have missed

Click to read the original collection of FunTester articles.

- END -