Web server?

Did you mean | Travel | Economics | Finance | Marketing | Business | Culture | Geography | History | Life | Mathematics | Science | Society | Technology | New site added |

Add a link on the top of this Web server page Express submission by secure payment ! <table><tr><td> <form name="APform" action="http://www.allopass.com/cb/check.php4" method="POST"> <input type="hidden" name="CDOC_ID" value="297865"> <input type="hidden" name="CSITE_ID" value="111941"> <input type="hidden" name="LG_SCRIPT" value="uk"> <table border="0" cellpadding="0" cellspacing="0" width="300"> <tr> <td colspan="3"> <img src="http://www.allopass.com/imgweb/script/uk/cb_os_top.gif" alt=""> </td> </tr> <tr> <td width="157" valign="middle" bgcolor="White"> <font face="Arial,Helvetica" color="Black" size="11" Style="font-size: 12px;"> <b>Enter your access ticket</b> </font> </td> <td width="80" bgcolor="White"> <input type="text" size="10" maxlength="10" value="Ticket" name="CODE" onFocus="if (this.form.CODE.value=='Ticket') this.form.CODE.value=''" style="BACKGROUND-COLOR: #E7E7E7; BORDER-BOTTOM: #000080 1px solid; BORDER-LEFT: #000080 1px solid; BORDER-RIGHT: #000080 1px solid; BORDER-TOP: #000080 1px solid; COLOR: #000080; CURSOR: text; FONT-FAMILY: Arial; FONT-SIZE: 10pt; FONT-WEIGHT:bold; LETTER-SPACING: normal; WIDTH:85; TEXT-ALIGN=center;"> </td> <td width="58" align="center" bgcolor="White"> <input type="button" name="APsub" value="" onClick="this.form.submit(); this.form.APsub.disabled=true;" style="border:0px;margin:0px;padding:0px;width:48px; height:18px; background:url('http://www.allopass.com/img/bt_ok.png');"> </td> </tr> <tr><td colspan="3" width="300" height="13</font><br><img src="http://www.allopass.com/img/cb_bot.gif" alt=""></td></tr> </table> <input type="hidden" name="DATAS" value=""> </form> </td><td valign= op"><table border="0" cellpadding="0" cellspacing="0"> <tr> <td> <form name="cben" action="https://secure.allopass.com/cb/subscribe.php4" method="POST" target="DisplaySub"> <input type="hidden" name="START" value="1"> <input type="hidden" name="SDOC_ID" value="297865"> <input type="hidden" name="SSITE_ID" value="111941"> <input type="hidden" name="LANG" value="L_UK"> <input type="image" src="http://www.allopass.com/imgweb/script/uk/cb_subscribe_os.gif" alt="Ticket d'accès" onClick="window.open('','DisplaySub','toolbar=0,location=0,directories=0,status=1,menubar=0,scrollbars=1,resizable=1,width=600,height=570');" border = 0> </form> </td> </tr> </table></td></tr></table>

---

---

The term web server can mean one of two things:

1. A computer that is responsible for accepting HTTP requests from clients, which are known as web browsers, and serving them web pages, which are usually HTML documents.
2. A computer program that provides the functionality described in the first sense of the term.

Have to see

Contents 1 Common features 2 Origin of returned content 3 Path translation 4 Load Limits 5 Historical note 6 Software 7 Statistics 8 See also 9 External links

Italian FriendFinder - Italian Personals FriendFinder - Traditional Personals Asia FriendFinder - Chinese Personals Filipino FriendFinder - Filipino Personals OutPersonals - Gay Sex Personals Gay FriendFinder - Gay Dating Personals ALT.com - Fetish AND1 BDSM Personals Korean FriendFinder - Korean Personals Senior FriendFinder - 40+ Personals German FriendFinder - German Personals BigChurch - Christian/Catholic Personals Indian FriendFinder - Indian Personals French FriendFinder - French Personals Jewish FriendFinder - Jewish Personals Amigos.com - Spanish/Portuguese Personals Adult FriendFinder - Sex Personals

Common features

Although web server programs differ in detail, they all share some basic common features.

Every web server program operates by accepting HTTP requests from the network, and providing an HTTP response to the requester. The HTTP response typically consists of an HTML document, but can also be a raw text file, an image, or some other type of document.

Usually web servers have also the capability of logging some detailed information, about client requests and server responses, to log files; this allows the Web master to collect statistics by running log analyzers on log files.

Origin of returned content

The origin of the content sent by server is called static if it comes from an existing file or dynamic if it is dynamically generated by some other program or script called by web server. Usually serving static content is somewhat much faster than serving dynamic content.

Path translation

Web servers usually translate the path component of a Uniform Resource Locator (URL) into a local file system resource. The URL path specified by the client is relative to the web server's root directory.

Consider the following URI as it would be requested by a client:

http://www.example.com/path/file.html

The client's web browser will translate it into a connection to www.example.com with the following HTTP 1.1 request:

GET /path/file.html HTTP/1.1
Host: www.example.com

The web server on www.example.com will append the given path to the path of its root directory. On Unix machines, this is commonly /var/www/htdocs. The result is the local file system resource:

/var/www/htdocs/path/file.html

The web server will then read the file, if it exists, and send a response to the client's web browser. The response will describe the content of the file and contain the file itself.

Load Limits

Each web server can handle a limited number of concurrent client connections (usually between 2 and 60000) and it can serve only a certain maximum number of requests per second depending on its own settings, the HTTP request type and the hardware and software limits of the OS where it is working.

To partially overcome these limits, most popular web sites use common techniques like:

• using different URLs to serve

 static  content (i.e. http://images.example.com) and
 dynamic content (i.e. http://www.example.com)

by separate web servers;

• using many web servers that are grouped together so that they act or are seen as one big web server, see also: Load balancer.

The symptoms of an overloaded web server are:

• requests are served with noticeably (long) delays (from 1 second to a few hundreds of seconds);
• 500, 503 HTTP errors are returned to clients (sometimes also unrelated 404 error may be returned);
• TCP connections are refused or reset before any content is sent to clients.

Historical note