Next, the Request Processor examines the request for session information. Session information is generally sent from the client -(the user's browser) to the server via cookies. The security/session handler is described in +(the user's browser) to the server via cookies. The security/session handler is described in detail in its own document. It examines the client request and either extracts or sets up new session tokens for the user.
@@ -51,7 +51,7 @@
extensions, i.e. files that end with: .html,
.tcl and .adp.
-If the RP can't find any matching files with the expected extensions,
+If the RP can't find any matching files with the expected extensions,
it will look for virtual-url-handler files, or .vuh
files. A .vuh file will be executed as if it were a Tcl
file, but with the tail end of the URL removed. This allows the code
@@ -63,8 +63,8 @@
described in OpenACS 4 Request Processor Design.
Once the appropriate file is found, it is either served directly if -it's static content, or sent to the template system or the standard -Tcl interpreter if it's a dynamic page. +it's static content, or sent to the template system or the standard +Tcl interpreter if it's a dynamic page.