how web server works
�
Let's say that you are sitting at your computer, surfing the Web, and you get a call from a friend who says, "I just read a great article! Type in this URL and check it out. It's at http://computer.howstuffworks.com/web-server.htm." So you type that URL into your browser and press return. And magically, no matter where in the world that URL lives, the page pops up on your screen.
At the most basic level possible, the following diagram shows the steps that brought that page to your screen:
# INCLUDEPICTURE "http://static.howstuffworks.com/gif/webserver-basic-sm.gif" \* MERGEFORMATINET ### Your browser formed a connection to a Web server, requested a page and received it.
Behind the Scenes
If you want to get into a bit more detail on the process of getting a Web page onto your computer screen, here are the basic steps that occurred behind the scenes:
The browser broke the URL into three parts:
The protocol ("http")
The server name ("www.howstuffworks.com")
The file name ("web-server.htm")
The browser communicated with a # HYPERLINK "http://computer.howstuffworks.com/dns.htm" #name server# to translate the server name "www.howstuffworks.com" into an IP Address, which it uses to connect to the server machine.
The browser then formed a connection to the server at that IP address on port 80. (We'll discuss ports later in this article.)
Following the HTTP protocol, the browser sent a GET request to the server, asking for the file "http://computer.howstuffworks.com/web-server.htm." (Note that cookies may be sent from browser to server with the GET request -- see # HYPERLINK "http://computer.howstuffworks.com/cookie.htm" #How Internet Cookies Work# for details.)
The server then sent the # HYPERLINK "http://computer.howstuffworks.com/web-page.htm" #HTML text# for the Web page to the browser. (# HYPERLINK "http://computer.howstuffworks.com/cookie.htm" #Cookies# may also be sent from server to browser in the header for the page.)
The browser read
Let's say that you are sitting at your computer, surfing the Web, and you get a call from a friend who says, "I just read a great article! Type in this URL and check it out. It's at http://computer.howstuffworks.com/web-server.htm." So you type that URL into your browser and press return. And magically, no matter where in the world that URL lives, the page pops up on your screen.
At the most basic level possible, the following diagram shows the steps that brought that page to your screen:
# INCLUDEPICTURE "http://static.howstuffworks.com/gif/webserver-basic-sm.gif" \* MERGEFORMATINET ### Your browser formed a connection to a Web server, requested a page and received it.
Behind the Scenes
If you want to get into a bit more detail on the process of getting a Web page onto your computer screen, here are the basic steps that occurred behind the scenes:
The browser broke the URL into three parts:
The protocol ("http")
The server name ("www.howstuffworks.com")
The file name ("web-server.htm")
The browser communicated with a # HYPERLINK "http://computer.howstuffworks.com/dns.htm" #name server# to translate the server name "www.howstuffworks.com" into an IP Address, which it uses to connect to the server machine.
The browser then formed a connection to the server at that IP address on port 80. (We'll discuss ports later in this article.)
Following the HTTP protocol, the browser sent a GET request to the server, asking for the file "http://computer.howstuffworks.com/web-server.htm." (Note that cookies may be sent from browser to server with the GET request -- see # HYPERLINK "http://computer.howstuffworks.com/cookie.htm" #How Internet Cookies Work# for details.)
The server then sent the # HYPERLINK "http://computer.howstuffworks.com/web-page.htm" #HTML text# for the Web page to the browser. (# HYPERLINK "http://computer.howstuffworks.com/cookie.htm" #Cookies# may also be sent from server to browser in the header for the page.)
The browser read