So in this, you know, we're going to talk about the history of this, so in order to request any results
from the server, we need to follow some certain format for questioning results.
Otherwise, your results will not be given by the Observer.
So there are many types of request type requests so far to get requests.
So that request is used to get a.
Results from the Web server and the post request user to post some details to the Web site like Fountas,
like Yancy's sign up forms and username, like are the details you will enter into the form.
And when you click on Sign Up or some other submit button, then these details will be sent to the website
and put a request is there to approve the files, putting the files on the web server.
If you have the access to upload any face, you can use this comment.
And the third option, if you have the access to delete any file on that Web server, you can use that
to record the request and the option to request.
Just tell you what the server allows you to request for.
So if this option says, get pushed and put, you need to you can perform all these three requests.
We cannot you cannot use that request.
So so that's what this options request is for you to request are the of the request types, the Web
server error.
And there is another request.
The card had to request a decision like that, but it does not get the content of the but the results.
So in that we actually get the results we want, but instead it will just take the current duty whether
the resources are available or not.
So let's take a look at this example.
First one is the D hole is a one Dataquest and B, the format of the request, because the first one
is the date.
So I want to get something and that is slash that.
So I want to get started shomer from the web server.
And what I want to do is I want to specify the protocol music.
So I want to the one.
That one.
So on that one is a newer version and 1.0 is the audio version.
The difference between these two is and actually B one by one keeps the connection alive after you requesting
a business.
So in HTP HDB 1.0, after you request a tumour or any file of the server sending the response, then
the correction will be closed.
So you need to again initiate the connection and then you need to ask any other offers.
So that's a disadvantage that will increase the load from the current.
That's why we need to be on point one.
So we didn't want to connect to as many, uh, files as as you want.
So that is a frustration.
Frustration is the question.
So you need to specify the request.
I need to specify the results you want.
I need you to specify the protocol you need to use.
And this is called parameters.
And this is a value and parameter name and the value.
So you can t user end user and means for which browser I am requesting the resource, if it is Firefox
is Mozilla and these are our brothers.
And if you request from this will produce, uh, Sacro, then Chrome will be act as user agent and the
hostess actual.
You need to you are requesting that the strategy.
So in our case tell Google dot com and accept is the content paper you want to accept in your extract.
So you are telling the observer that I am ready to accept this picture and also I can accept images
and gifts.
So the surrounding this, it was a legitimate form of this.
And accept language, so I want to.
Get this, the turmoil in the English language, you can see your transfer for United States English,
so I want that to start to be in English language.
I mean, the content of that is that it should be in English.
You can also mention any other format if that format is available, or you can just Google translate
it and accept encoding with d.g.
And so there's a real sense in this encoding format and browser will do it for you and the content is
fifty fifty.
But this is the size of this special attachment and connection.
So keep in mind after this, requesting you after you send this request, you get the response on the
Web browser and again you can send the request without initiating any other connection.
That means one connection.
You can send multiple requests and responses and you don't you can send any parameters you want to send
to observer.
So since this is our request, we don't need to send any parameters in the most other situations.
So that's another example of the post request.
You can see the post.
So what I'm going to do is I'm posting some data to this not legitimate for the Web server side.
And the protocol I'm using is actually beyond.
So are these, uh, parameter names and the same user agent hashtags of extra legitimate?
An excerpt.
I want language in English and character so up to here to do so.
And then you can see there is a line called this is the actual data yourself and username and password
is clinical.
So this data will be sent in to these other observers.
It so set on seeing this post request, it will take these parameters and pass it to the log.
So in this way, it will have some server side, uh, like BHB programming language that this username
and password will be checked and then the response will either login success or failure will be sent
to the client.
So once again, we are just changing that to post to post some data to the Web server so you can send
the data as the variable name and the value and separated end and person.
And the name is name and value.
Is there a miscommunication or is going to be good?
So in this way, if you don't have a browser, you can also send out some online tools, some of those
tools in the later videos.
So the terrible question, I hope you have understood this one.