GET is used to retrieve and request data from a specified resource in a server. The HEAD request method is useful in recovering meta-data that is written according to the headers, without transferring the entire content. The technique is commonly used when testing hypertext links for accessibility, validity, and recent modification.
In web communication, POST requests are utilized to send data to a server to create or update a resource. One example is when a user uploads a profile photo. The difference between the two is that PUT requests are idempotent. This means that if you call the same PUT requests multiple times, the results will always be the same. However, its primary purpose is to apply partial modifications to the resource.
TRACE requests are used to invoke a remote, application loop-back test along the path to the target resource. The TRACE method allows clients to view whatever message is being received at the other end of the request chain so that they can use the information for testing or diagnostic functions. All these requests are routed through various routers and switches.
The domain name servers keep tables of machine names and their IP addresses, so when you type in Google. When you want to view any page on the Web, you must initiate the activity by requesting a page using your browser. The browser asks a domain name server to translate the domain name you requested into an IP address. The server should constantly be connected to the Internet, ready to serve pages to visitors.
When it receives a request, it looks for the requested document and returns it to the Web browser. When a request is made, the server usually logs the client's IP address, the document requested, and the date and time it was requested.
This information varies server to server. It's basically like the street between your house and the shop. This is like the transport mechanisms that let you place an order, go to the shop, and buy your goods. In our example, this is like a car or a bike or however else you might get around. When you type a web address in your browser, the browser looks at the DNS to find the website's real address before it can retrieve the website. The browser needs to find out which server the website lives on, so it can send HTTP messages to the right place see below.
This is like looking up the address of the shop so you can access it. HTTP : Hypertext Transfer Protocol is an application protocol that defines a language for clients and servers to speak to each other. This is like the language you use to order your goods. Component files : A website is made up of many different files, which are like the different parts of the goods you buy from the shop. Assets : This is a collective name for all the other stuff that makes up a website, such as images, music, video, Word documents, and PDFs.
When you type a web address into your browser for our analogy that's like walking to the shop : The browser goes to the DNS server, and finds the real address of the server that the website lives on you find the address of the shop.
The browser sends an HTTP request message to the server, asking it to send a copy of the website to the client you go to the shop and order your goods. If the server approves the client's request, the server sends the client a " OK" message, which means "Of course you can look at that website!
Here it is", and then starts sending the website's files to the browser as a series of small chunks called data packets the shop gives you your goods, and you bring them back to your house. The browser assembles the small chunks into a complete web page and displays it to you the goods arrive at your door — new shiny stuff, awesome! As the browser builds the DOM tree and applies the styles from the CSSOM tree and executes the JavaScript, a visual representation of the page is painted to the screen, and the user sees the page content and can begin to interact with it.
0コメント