Download Oracle WebServer User's Guide
Transcript
File Memory Mapping The Web Listener uses the host operating system’s memory mapping capability when opening a file requested by a client so that the Web Listener’s virtual address space refers directly to the file’s contents. This speeds access, and makes it possible for several clients to share the same copy of the file, which conserves the Web Listener’s memory resources. File Caching Ordinarily, when the Web Listener opens a requested file, the file remains open and mapped into memory until all clients using the file are finished with it, at which point the Web Listener closes the file and frees the memory mapping associated with it. The Web Listener allows you to specify files to be cached. Cached files are opened when a client requests them, and remain open for the life of the Web Listener process. This optimizes access times for files, such as your home page, that are requested often. File Protection The Oracle Web Listener allows you to make secure specific virtual files or directories by assigning authentication and/or restriction schemes to protect them. Authentication Schemes When a file or directory is protected by an authentication scheme, a client requesting access to it must provide a user name and password. Authentication schemes allow you to define named groups of user name/password combinations, and named realms that are groups of these groups. You can then assign user, group, and realm names to virtual files and directories, requiring any client requesting access to input one of the specified user name/password combinations. The Web Listener supports two authentication schemes: basic authentication and digest authentication. Both schemes are identical, except that digest authentication transmits passwords from client to server in an encrypted form called a digest, whereas basic authentication sends unencrypted passwords, making it considerably less secure. Some older web browsers don’t support digest authentication, but for files or directories that require authentication, you should use digest authentication whenever possible. Oracle WebServer Concepts 1-5