A HTTP Response is defined as three components: a status code, header, and body.
A number representing the state of the response.
When a web server responds to your browser, the first thing it tells you is how everything went. a 200 response means everything is good. A 500 response means the web server broke, sorry. A 400 response means that you made a mistake. A 300 response means we're confused.
The web is built on machines communicating their status to each other.
A header is metadata that describes the response. The web is multimedia. We deliver text, and hypertext, and images, and sound, and video, and binary and lolcatz. Data comes in many forms and we handle it all. To make things easy, we describe the data we deliver. Generally, you have to at least specify the type of content your sending back. Sometimes, you have to say more.
The body is actual data we want to send. Content is king and it lives in the body of the response. For a web page it's a bunch of HTML. For lots of other stuff, it's a bunch of binary data. But you already know that all data is just bits and characters, so binary, text, images, it's really all the same.
HTTP/1.0 200
This indicates that it is a HTTP response, and the corresponding status of the response.
Allow: GET, POST
Server: WebSitePro/2.0.41
Date: Mon, 19 July 2008 10:15:23 GMT
Server-Name: avi.flatironschool
From: [email protected]
Content-Length: 654
These are the headers of the HTTP response. They simply are a collection of metadata that help to describe the parameters of the response.
<html>
<h1>Everything is Awesome</h1>
</html>
Finally, this is the body of the response.
HTTP/1.0 200
Allow: GET, POST
Server: WebSitePro/2.0.41
Date: Mon, 19 July 2008 10:15:23 GMT
Server-Name: avi.flatironschool
From: [email protected]
Content-Length: 654
<html>
<h1>Everything is Awesome</h1>
</html>
View HTTP Response on Learn.co and start learning to code for free.
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent