Tweet
Hi,
The naming server returns the IP address to the browser which uses the IP address to contact the Web server associated with the address. Many web pages contain references to other files that the Web server must provide for the page to be complete however, the browser can request only one file at a time. For example, images referenced in a Web page require a separate request for each image. Thus, the process of displaying a Web page is usually a series of short conversations between the browser and the server. Typically, the browser receives the main page, searches it for other required file references, and then begins to display the main page while requesting the referenced files. That is why you often see image placeholders when a page is loading. The main page contains the references to other URLs that contain the images, but not the images themselves. What the Server does with the request. From the Web server point of view, each conversation is brand new contact.
By default, a Web server services requests on a first come, first served basis. Web servers do not remember any specific browser form one request to another. Parts of a URL the line that you type into the browser address field is a Uniform Resource Locator. The server breaks the requested URL into its component parts. Forward slashes, colons, periods, question marks, and ampersands, called delimiters, make it easy to separate the parts. Each part has a specific function. Server Translates the Path You do not make Web request with real or physical paths instead, you request pages using a virtual path. After parsing the URL, the server translates the virtual path to a physical path name. Server Checks for the Resource the server checks for the requested file. If it does not exist, the server returns an error message. You have probably seen this error message while browsing the web if not, you are luckier than I am. Server Checks Permissions After locating the resource, the server checks to see if the requesting account has sufficient permission to access the resource. For example, if the requesting account is the anonymous account, and the user has requested a file for which that account has no read permission, the server returns an error message. The actual error text depends on the exact error generated.
There are several sub levels for error messages. You can find a complete list of error messages in the IIS Default Web Site Property dialog box. The contents of most error messages are customizable. By default, the server reads error messages text from the HTML files in your windows directory, where windows are the name of your NT directory, usually named Want. How the Server Responds? Graphics files, Word documents, HTML files, ASP files, executable files, CGI Scripts how does the server know how to process the requested file? Actually, server differentiates file types in several different ways. Internet Information Server differentiates file types based on file extensions just like windows Explorer.
The naming server returns the IP address to the browser which uses the IP address to contact the Web server associated with the address. Many web pages contain references to other files that the Web server must provide for the page to be complete however, the browser can request only one file at a time. For example, images referenced in a Web page require a separate request for each image. Thus, the process of displaying a Web page is usually a series of short conversations between the browser and the server. Typically, the browser receives the main page, searches it for other required file references, and then begins to display the main page while requesting the referenced files. That is why you often see image placeholders when a page is loading. The main page contains the references to other URLs that contain the images, but not the images themselves. What the Server does with the request. From the Web server point of view, each conversation is brand new contact.
By default, a Web server services requests on a first come, first served basis. Web servers do not remember any specific browser form one request to another. Parts of a URL the line that you type into the browser address field is a Uniform Resource Locator. The server breaks the requested URL into its component parts. Forward slashes, colons, periods, question marks, and ampersands, called delimiters, make it easy to separate the parts. Each part has a specific function. Server Translates the Path You do not make Web request with real or physical paths instead, you request pages using a virtual path. After parsing the URL, the server translates the virtual path to a physical path name. Server Checks for the Resource the server checks for the requested file. If it does not exist, the server returns an error message. You have probably seen this error message while browsing the web if not, you are luckier than I am. Server Checks Permissions After locating the resource, the server checks to see if the requesting account has sufficient permission to access the resource. For example, if the requesting account is the anonymous account, and the user has requested a file for which that account has no read permission, the server returns an error message. The actual error text depends on the exact error generated.
There are several sub levels for error messages. You can find a complete list of error messages in the IIS Default Web Site Property dialog box. The contents of most error messages are customizable. By default, the server reads error messages text from the HTML files in your windows directory, where windows are the name of your NT directory, usually named Want. How the Server Responds? Graphics files, Word documents, HTML files, ASP files, executable files, CGI Scripts how does the server know how to process the requested file? Actually, server differentiates file types in several different ways. Internet Information Server differentiates file types based on file extensions just like windows Explorer.
Comment