Now that you've seen a few sample HTTP requests using telnet,

I'd like to show you the overall format of an HTTP request

as stated in the specifications which I've linked to in the teacher's notes.

Here's how an HTTP request needs to look.

HTTP request begin with request line.

This starts with what's called the request method, get or post.

Know that there are other request methods available on HTTP.

They're outside the scope of this course but

I've linked to them in case you're curious.

In general the get request method is used when you want to

view a resource on the server without making any changes.

And post request are used for actually making a change or

update to the listed resource.

We'll look at post request later in the course.

Speaking of the resource, that's what's listed next, the URI, or

again, Uniform Resource Identifier.

If you want to view the root, or

what's typically the home page, you'll use a single slash here.

Finally, HTTP is listed as the protocol in use followed by a slash and

ending with the version of HTTP, currently 1.1.

As a side note and heads up, HTTP/2 is on the way.

Don't worry though,

HTTP/2 won't change any of the stuff we're discussing in this course.

And you'll be able to continue using HTTP/1.1 likely for many years to come.

For more info on HTTP/2, check the teacher's notes.

The next line begins with what's called the header section of the request.

This communicates information related to the request being made, and

can include all sorts of info.

In this example, you see it includes the host which we've discussed.

The user agent which identifies the exact device making the request

I've listed telnet here and

accept language which tells the server which language we prefer for the response.

There are lots of other headers available and

we'll see a bunch more throughout the best of the course.

Following the headers is a blank line.

Then concluding the request, is the request body, or

what's frequently called the payload.

If the headers refer to the information related to the request,

the payload refers to the data being transferred in the request, if any.

As we'll see, data needs to be transferred when the purpose of the request

is to change a resource on the server.

For example, consider the scenario of using a form to

edit the first name of a contact saved in your address book online.

When you submit those changes,

a post request is sent containing the new first name in the payload.

In general, the exact changes to be made on the server

will be contained in the payload of the post request.

You won't see a payload in the get request.

And there you have it, the format for any HTTP request.

With that said,

let's turn to the other side of this web conversation, the response.