By the end of this chapter, you should be able to:
https://www.rithmschool.cominto your browser's URL bar and press enter
At a high level, the HTTP spec involves a computer making a request for some information at a URL. The request goes to a web server (another computer) somewhere on the Internet. The web server handles that request and then sends back the appropriate data to the requesting computer.
Taking the example of
https://www.rithmschool.com, let's look at what happens in a little more detail. What happens when you type that address in your browser window? What are the steps that bring you back a viewable web page? Here's an overview:
https://www.rithmschool.cominto an IP address (e.g. 22.214.171.124). Once the browser has an IP address, it can make a connection to the server. IP addresses aren't easy to remember like URLs, which is why they're typically abstracted away from humans.
/. We will talk about the GET request in more details later.
200, and a response body. The body of the HTTP response is the HTML text that will be displayed in the browser.
<!DOCTYPE HTML>tag, the browser reads the response body line by line and creates an in memory representation of the HTML document called the DOM.
<script src="main.js">is a reference to another file on the server. In order to use the resource, the browser must make additional GET requests.
The basics of the request-response cycle are often diagrammed chronologically, with the client on the left and the server on the right:
In this diagram, the client first makes a request to "/", and the server responds with a status code of 200 and some HTML. Presumably within that HTML there's a script tag with an
src attribute set to "main.js", so the client then makes a second request. The server once again responds with a status code of 200.
When you're ready, move on to HTTP and REST