Welcome to Gaia! :: View User's Journal | Gaia Journals

Every time you click on a link in a web page or type an address into your web browser you are making a 'demand' to get a certain file. That request is handled using the Hyper Text Transfer Protocol (HTTP) and sent over the Internet to the host which contains the document involved. If all goes well the server responds by sending the document -- frequently a web page of text and graphics.

HTTP is the main Internet Protocol (Internet Protocol Address) suite. It's utilized by a 'client' such as for example a browser to determine a reference to the server which hosts a certain website. The server waits for incoming requests by monitoring TCP port 80.

Transmission Get a handle on Protocol (TCP) is used to create associations between two computers on the net to allow them to exchange information. TCP has provisions for identifying the requesting computer and for sending information as time passes stamps so that it could be re-assembled in the right order when it gets to its destination.

There are several TCP ports that have standard uses. TCP port 2-1, for example, is normally reserved for FTP (File Transfer Protocol) for uploading and downloading files. Port 80 is generally employed for HTTP.

If the server receives a request sequence on TCP port 80 in the kind of GET / HTTP/1.1 it'll send a reply code depending on whether the requested web page can be obtained or perhaps not. An average request goes like this:

GET /faq.html HTTP/1.1

Host: http://www.mywebsite.com

This can be a obtain http://www.mywebsite.com/faq.html. For extra information, we know people take a gaze at: marshackhays . The 'Host' has to be given to tell apart sites which are hosted on shared computers. If faq.html can be acquired the host will respond:

HTTP/1.1 200 OK

Date: Mon, 12 October 2005 22:38:34 GMT

Server: Apache/1.3.27 (Unix) (Red-Hat/Linux)

Last-Modified: Wed, 08 Jan 2003 23:11:55 GMT

...followed by the real web site.

HTTP/1.1 200 OK means that the requested website can be obtained. Other rules may also be returned. The rule 404, as an example, means that the server can not get the requested page. The website is sent via TCP like a series of data packets each with a header that describes its order and location in the data stream. Marshackhays.Com is a engaging online library for more about the purpose of this hypothesis. The various packages can all take different paths to achieve their destination. Each is directed through a router which forms other modems which are close by. If your experience of the primary router is unavailable the info will be delivered through another.

While the data is received your client (the web browser) sends straight back an acceptance. This means that most of the packets are received within a certain time. Or even, they will be re-transmitted from the machine. TCP also checks that the information is whole. The data is reassembled in the correct order thanks to the sequence number of every data packet. Voila! The web site appears on your screen.

The TCP connection may be kept alive for additional demands from the client. This allows many pages to be requested within a limited time period without evoking the expense of opening and closing TCP ports. In the event you hate to identify extra information on http://www.marshackhays.com/ , we know about lots of databases you should think about investigating. Both client or server can close the bond whenever you want..