Request-Handling Process Overview

                                                                                                                                                                                                                                                                                                                                      Back to [Book]     [Topic]

Request-Handling Process Overview

When Web Server first starts up, it performs some initialization tasks and then waits for an HTTP request from a client (such as a browser). When the server receives a request, it first selects a virtual server. The obj.conf file of the selected virtual server determines how the server handles a request.

The obj.conf file contains a series of instructions known as directives that tell the server what to do at each stage in the request-handling process. These directives are grouped inside Object tags. Each directive invokes a function with one or more arguments.

Each directive applies to a specific stage in the request-handling process. For example, a directive that applies during the authorization stage in the request-handling process is an AuthTrans directive.

Stages in the Request-Handling Process

Stages Description
AuthTrans (authorization translation) Verify the authorization information (such as name and password) sent in the request.
NameTrans (name translation) Translate the logical URI into a local file system path.
PathCheck (path checking) Check the local file system path for validity and check if the requestor has access privileges to the requested resource on the file system.
ObjectType (object typing) Determine the Multipurpose Internet Mail Encoding (MIME) type of the requested resource (for example, text/html, image/gif, and so on), and establish other resource-specific settings.
Input (prepare to read input) Select filters that will process incoming request data read by the Service step.
Output (prepare to send output) Select filters that will process outgoing response data generated by the Service step.
Route (request routing) Select the server to service the request.
Service (generate the response) Generate and return the response to the client.
AddLog (adding log entries) Add entries to log files.
Error (error handling) Send an error message to the client and exit processing. This step is executed only if an error occurs in the previous steps.

Labels

configurationfile configurationfile Delete
+configguide +configguide Delete
java java Delete
server server Delete
configuration configuration Delete
administrator's administrator's Delete
webserver webserver Delete
sun sun Delete
application application Delete
system system Delete
webtier webtier Delete
guide guide Delete
file file Delete
webserver70 webserver70 Delete
sunjava sunjava Delete
filereference filereference Delete
web web Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Sign up or Log in to add a comment or watch this page.


The individuals who post here are part of the extended Sun Microsystems community and they might not be employed or in any way formally affiliated with Sun Microsystems. The opinions expressed here are their own, are not necessarily reviewed in advance by anyone but the individual authors, and neither Sun nor any other party necessarily agrees with them.

Copyright 1994-2009 Sun Microsystems, Inc.
Powered by Atlassian Confluence
Sun Guidelines on Public Discourse Privacy Policy Terms of Use Trademarks Site Map Employment Investor Relations Contact