The back end, on the other hand, is all of the parts of the web the users do not directly interact with.

In this video, we're going to discuss the basics of how the back end of a website works by tracing all of the steps that the back and must go through from the moment it receives a request to the point, it sends a response back to the client.

Starting at the beginning, the silver will receive a request from a client in the form of a euro.

From this euro, the server could get almost all of the information it needs in order to process a request.

Let's break apart a typical girl at the beginning.

We have the protocol for the request.

The only thing that the protocol does is tell the server.

If the request is encrypted.

Http is for standard non encrypted request and https is burn crypt ID request other than telling the server at the response is encrypted or not, the protocol doesn't affect the way the server handles request and can't be ignored.

Next, we have the host, also known as the domain name, again.

This is not important to worry about for the server, since all it does is tell the Internet which server to send the response to each server has their own particular host.

So once the request actually gets to the server, the host does not matter, since all requests for the server will have the same host.

For example, YouTube dot com is the host for the YouTube server, so the YouTube server already knows that all request it gets will have the host youtube dot com.

This means that we can safely ignore the first half of the earl, which weighs us with last two sections of the euro, the path and the query string.

The PATH tells the server with the client wants and defines which section of code on the server should be run in order to get the correct response.

Essentially, the server is broken down into a bunch of different sections, which all correspond to a specific path.

Lastly, the quarry string is used by the specific section of the server toe.

Alter the response.

The query string is broken down into specific query parameters, which can augment the way that the server responds to a request for a specific path.

For example, YouTube uses the same path when you search for a video.

But the query string contains a search query perimeter, which tells the server what you search for so it can respond with what you want.

The euro alone is not enough to tell the server exactly what it needs to do, though it can tell the server which section to look for and how to alter that section based on the query parameters.

But that section of the server is broken down even further into multiple different parts.

To determine which part of that section the service should run, it needs to use an action, which is passed along with the euro.

This action can either be get post put or delete.

By combining the action and this path, the server confined the correct part of the correct section that it needs to run.

It can then use the query parameters toe alter the response of that particular part and section.

Normally, the response from the server will be an HTML page that is dynamically generated based on the request from the client.

This is why, when you go to the YouTube search page, it always shows you the same page, since it has the same pat and action.

But the videos that have returned from your search are different, based on the query parameter for your search.

Another important thing to note about a server is that is only accessible to the outside world through this sections that it defines.

This means that you can store any secure information on the server and we'll be safe as long as it is not exposed through a specific path.

This is why it is safe to have a database and a website running on the same server.

Since the server on Lee chooses to expose the website and not the database.

Essentially, the server axes a barrier between the outside world and all the parts of a website, and that's all you need to know about how the back end of a Web server works, and the next video we're going to be talking about rest and how modern websites used rest for your ills in order to make handling resource is and request much easier.

Make sure to check out that video link over here when it comes out and subscribe to the channel.

So you don't miss any more videos in this series.

Thank you very much for watching and have a good day.