How do we communicate with our website?
Most of you probably know this already, but I will mention it in this video just so we can get a quick
refresher.
We explained all of these attacks in the previous video, but it's important we know the basics behind
communication between a client and a website.
So we send requests and receive pages back with the help of HTTP requests and HTP responses.
HTTP request is something that we send to the website once we want to get a certain Web page from that
website and HTP response is a response from the website telling us that either it found the page that
we were looking for or it didn't.
HTP response also contains an HTML code of the Web page that we requested.
Now this would be a basic explanation of the process, but let us also take a look at how an HTP request
and an HTP response look like.
So if we take a look at this image right here in the red letters, we can see HTP request to some Web
page while in deep blue letters we see and HTTP response.
Let us focus first on HTTP request, so some of the known fields from the request would be fonts you
see in the image we got hosts and that field defines the website domain that you are searching for.
Sometimes this field can also have a port number due to Web servers, sometimes hosting more than one
website.
Besides that, we also got the user agent field and this field is used by server to identify the client
that is connecting to the server.
By identifying I mean, it would usually identify the Web browser that the client is using.
HTP request can also have cookies, which we can see here in this picture, but what cookies are our
values exchange between a client and the server that are used for holding data and information about
a certain session that the user has?
Sometimes and HTP request can also have authorisation parameter, which is used to check for the identity
with this parameter, usernames and passwords are sent to the website.
On the other hand, we got and HTP response, which also has some special fields of its own.
First thing we see is the status code.
Now, a field called status quo doesn't exist, but the value will be stored in the first line of the
response most of you encountered at some point and fall for error.
Once you try to search for a certain Web page and fall for in this case is a status code.
In this picture we can see a status code of two hundred, which indicates that the page exists and therefore
loaded it successfully.
Besides this, we got set cookie field and this field, if defined, will establish values of cookies
to the client.
This value server can use later to identify the client and to also store clients data.
We also got field called cash control, and this field is used if the content of the response should
get stored inside the browser of the client or not.
And we also got content that will tell us the size of the response in Bite's.
Below all of these fields, we can see HTML tags opening and down there is the Web page that we requested
from this website.
It sends us the Web page code that will then get rendered inside of our browser and it will show us
the Web page.
Simple as that.
Great.
Now, that will refresh our memory about this.
Let us finally start attacking websites.
See you in the next video.