Original subtitles

But before we jump into the hacking, I want to talk about the basics of an HGP request, what happens

when you type in a Web address into your browser?

What information is sent to these Web server and while you receive back in return.

So when you visit in the Homestake dot com, my personal website, your browser is sending a request

to the Web RWD, which is a slash saying this is the host, this is a user agent.

I have, for example, I'm using Firefox and it's going to say this is what I'm expecting to accept.

There's going to be an authorization perhaps, where you authorize yourself because you're already logged

in and it's going to also have a referral.

That means the website that you already coming from.

So if you on Google looking for my website and you click on it, my website is going to know where you're

coming from.

So just to break it down again, the first one is the endpoint.

That's the page you're fetching.

So if you're looking at your profile, it will be something like profile that profile your user ID.

The next one is the host.

Again, this is the website you are fetching.

The third thing, user agent is the browser you're using Sattell, the web server.

This is a browser I have give me the best version of the website destitutes, my browser.

And the next one is what type of content you want to receive, which is the content type, as I mentioned,

authorization.

This is where you authorize yourself, if you're already logged into this website is going to say,

hey, I have an authorization code.

Here it is.

Let me be logged in.

And the referrer is the website where you were referred to the next one.

But as you saw in the last slide, there is a keyword called Get.

I mean that I'm saying get this page for me.

I want you to fetch this data from this page, but you can also make other requests.

For example, if you post requests that meat could be that you're creating or changing data with a put

request.

It means you're replacing or modifying some sort of a data deleting, as obvious as it sounds or to

delete some data and options is to communicate to see what options does that particular endpoint take.

And there's also had this one is the same as yet, but it doesn't show you a response.

It just requests to see if that pages there or not.

So it doesn't give you a response at all.

It just looks to see if that page is available.

When you make a request to a Web server, the server is going to respond with a variety of ranges.

Each of these mean different things and it kind of that's your browser, know what to expect.

So, again, if you make a request to a webroot and the page is available, it's going to be in the

200 ranges.

If you go to a website and it redirects you to another page, that's going to come back as to 300.

And if you are unauthorized, maybe you don't have access to this resource.

The page is there or the method you are using is not allowed that it's going to be within the 400 range.

There's also the last one was 500.

This is where the server doesn't know how to handle your request.

And it comes back and says, hey, I don't know what to do with this request.

There is an error.

Fix it.

It's a very important for you to understand as you get into your hacking.

So I highly recommend getting familiar with each response status code.

You can go to Mozilla's website, as I put it, in the resource section of this course, and kind of

get familiar what each one means.

Or if you come up with them and you see them while you're hiking, you can look them up and learn more

about them.