| Previous Contents Index Next |
| iPlanet Web Server: FastTrack Edition Administrator's Guide |
The Install a New PKCS#11 Module Page
The Server Manager allows you to manage an iPlanet Web Server instance. To access the Server Manager, complete the following steps:
Click the Servers tab in the Administration Server.
To access the Server Manager directly without going through iPlanet Web Administration Server, type the following URL from a browser:Click Manage Servers. The Manage Servers page appears.
Select the iPlanet Web Server instance you want to manage, and click Manage. The Server Manager page appears.
http://hostname.domain-name:administration_port/server_name/bin/index
The Server Manager contains the following tabs:
The Preferences Tab
The Preferences Tab
The Preferences tab allows you to configure server preferences, control file access on your web site, and enable Secure Sockets Layer (SSL) to ensure privacy when communicating with other SSL-enabled products. The Preferences Tab contains the following pages:
The Server On/Off Page
The Restore Configuration Page
The Native Thread Pool Page (NT)
The Custom Error Responses Page
The Dynamic Configuration Files Page
The Access Control List Management Page
The Access Control List Management Page
The Server On/Off Page
The Server On/Off page displays the current status of the server and allows you to start or stop the server.For more information, see Starting and Stopping the Server.
The following elements are displayed:
Server On. Starts the server so that all listening ports are waiting for client connections.
Server Off. Shuts the server down and stops all running processes. After you shut down the server, it may take a few seconds for the server to complete its shut-down process and for the status to change to off.
About This Server. Displays server version and third-party software information in the Version Information page.
The View Server Settings Page
The View Server Settings page allows you to configure the technical and content settings in the magnus.conf and obj.conf configuration files. Click any link to change the setting.For more information, see Viewing Server Settings.
The following elements are displayed:
Server Root. Specifies the path in which the server's binaries are stored.
Hostname. Specifies the fully qualified host name of this server (for example, www.mozilla.com).
Port. Specifies the port number servicing HTTP requests when no specific port number is specified. The default is port 80.
Error Log. Specifies the location of the error log. The error log captures all the requests which resulted in an error.
User (Unix/Linux). Specifies the user name under which the server runs. The server user should have restricted access to your system resources. You can often use a user named nobody in this situation. On some systems, however, nobody is not a valid user name. You may not want to give the user nobody group access to all files. If you do not use nobody, create a new Unix/Linux user, such as adm, to be the server user.
MTA Host. Specifies the name of the mail server that this server uses to send mail.
DNS. Allows you to enable the server to do a reverse lookup of a client's IP in the DNS database before executing a CGI script. Servlets also depend on this flag to do reverse lookup.
Security. Specifies whether SSL is running on this server.
NSAPI Library. Displays the absolute path to the NSAPI library.
NSAPI Functions. Displays the NSAPI functions called in the obj.conf file.
Additional Document Directory. Lists the additional directory path to the location of the server's web documents.
NSAPI. Displays the names and arguments of the server's NSAPIs.
Primary Document Directory. Specifies the root directory for documents. You need to change this value only if you change the root directory for documents in the Content Management page.
Restrict Access. Specifies whether access control lists (ACLs) are enabled. ACLs allow you to protect files or directories by implementing access control by user name, password, domain name, or IP address.
Index Filenames. Specifies the names of the file that the browser displays when no file name is specified in a URL. The file names are listed in order of preference.
Default MIME Type. Specifies the MIME type used if a file extension does not match any of the MIME types specified in mime.types file.
Directory Indexing. Specifies the default method for displaying the contents of a directory when there is no file matching one of the default file names. Choose a value from the drop-down list:
Fancy. Displays each directory entry as a hyperlink with the file size, the last modified time, and an icon next to each entry to indicate the file type.
Access Log. Specifies the path to the server access log. The access log captures all incoming requests to a server.Simple. Displays directory entries as plain text hyperlinks.
For the Style. Specifies information regarding the style, such as whether ACLs are enabled, the location of the NSAPI library, and so on.
The Restore Configuration Page
The Restore Configuration page allows you to view a backup copy of your configuration files and revert to the configuration data saved on a specific date.
Note On Windows NT, use this page only to roll back your own changes to the configuration files. Do not roll back to backup versions created during installation; they may not be complete.
The following elements are displayed:
Set number of sets of backups. Specifies the number of sets of backups. Click Change to apply the change.
In the following table, click Restore to revert to the version saved on the specified date, or click View to preview the settings before choosing to revert. Click a date button to restore all working files to what they were on the selected date. You can restore the following configuration files:
https-server_name.acl. Contains the server access control lists.
magnus.conf. Contains global settings that the server uses for initialization.
obj.conf. Defines specific steps that the server takes to process instructions. In this file, you can specify path translations, and define how things such as cgi and servlet programs are handled.
mime.types. Specifies the path to the file containing the mapping of MIME types returned by the server.
jvml2.conf. Contains the configuration for the Java virtual machine (JVM).
servlets.properties. Contains the name of each servlet and its initialization parameters.
rules.properties. Contains virtual paths for servlets.
webpub.conf. Contains the system settings and file paths. In your server's obj.conf file, the search system initialization is mapped to the webpub.conf file. When you use the Search Configuration and Search Pattern Files pages, the data you input is reflected in the webpub.conf file.
The Performance Tuning Page
The Performance Tuning page allows you to configure the server to optimize its performance.For more information, see Performance Configuration.
The following elements are displayed:
Maximum Simultaneous Requests. Specifies an upper limit on the number of simultaneous requests accepted by the server. When a new request arrives, the server checks to see if it is already processing the maximum number of requests. If it has reached the limit, it defers processing new requests until the number of active requests drops below the maximum amount. Default is 512.
DNS Enabled. Allows you to enable the server to do a reverse lookup of a client's IP in the DNS database before executing a CGI script. Servlets also depend on this flag to do reverse lookup. DNS lookups can slow performance, especially on a server that uses extensive CGI. By default, DNS lookups are not allowed. Instead, hosts are identified by IP address in the CGI environment and in log files.
Async DNS Enabled. Specifies whether asynchronous DNS is enabled. DNS causes multiple threads to be serialized when you use DNS services. If you do not want serialization, enable asynchronous DNS. You can enable it only if you have also enabled DNS. Enabling asynchronous DNS can improve your system's performance if you are using DNS.
DNS Cache Enabled. Determines whether to cache DNS entries. If you enable the DNS cache, the server can store hostname information after receiving it. If the server needs information about the client in the future, the information is cached and available without further querying. Caching DNS entries may slow down the server.
Size of DNS cache. Specifies the size of the DNS cache if you have enabled DNS. The DNS cache can contain 32 to 32768 entries; the default value is 512 entries.
Expire entries (sec). Specifies the number of seconds to allow before DNS entries are deleted from the cache if you have enabled DNS. Cache entry expiration time can range from 1 second to 1 year (specified in seconds); the default value is 1200 seconds (20 minutes).
Listen Queue Size. Determines the size of the socket-level parameter that specifies the number of incoming connections the system will accept for that socket. If you manage a heavily used web site, make sure your system's listen-queue size is large enough to accommodate the listen-queue size setting from iPlanet Web Server. Setting the listen-queue size too high can degrade server performance. The listen-queue size was designed to prevent the server from becoming overloaded with connections it cannot handle. If your server is overloaded and you increase the listen-queue size, the server will only fall further behind.
The default setting is 128 (for Unix/Linux) or 100 (for Windows NT) incoming connections.
HTTP Persistent Connection Timeout. Specifies the number of seconds the server will allow a client connection to remain open with no activity. A web client may keep a connection to the server open so that multiple requests to one server can be serviced by one network connection. Since a given server can handle a finite number of open connections (limited by active threads), a high number of open connections will prevent new clients from connecting. Setting the timeout to a lower value, however, may prevent the transfer of large files as timeout does not refer to the time that the connection has been idle. For example, if you are using a 2400 baud modem, and the request timeout is set to 180 seconds, then the maximum file size that can be transferred before the connection is closed is 432000 bits (2400 multiplied by 180).
OK. Saves your entries. You must click Apply on the top right side of the page for your changes to take effect. If you do not click Apply after you update information, your changes are retained so that you can view and edit it, even though the changes have not taken effect.
Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.
The Native Thread Pool Page (NT)
The Native Thread Pool page allows you to configure your native thread pool (NativePool). By default, the server has at least one thread pool, the native thread pool. This thread pool is the default thread pool for external plugins, unless specified otherwise. It uses fibers (user-scheduled threads) for internal request processing.Minimum Threads. Determines the minimum number of threads in the native thread pool. If unspecified, defaults to 1.
Maximum Threads. Determines the maximum number of threads in the native thread pool. If unspecified, defaults to 128. If you specify 1, you emulate single-threaded behavior. [Note that iPlanet Web Server 4.1, FastTrack Edition, is limited to 5 concurrent threads.]
Queue Size. Determines the number of threads that can wait in the queue for the thread pool. If all threads in the pool are busy, the next request-handling thread that tries to get in the queue is rejected, with the result that it returns a busy response to the client. It is then free to handle another incoming request instead of being tied up waiting in the queue. If unspecified, defaults to an unlimited size.
Stack Size (bytes). Determines the stack size of each thread in the native thread pool. The minimum value you can enter is 65536. Entering 0 specifies the default stack size for the operating system.
OK. Saves your entries. You must click Save and Apply for your changes to take effect.
Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.
The Thread Pools Page
The Thread Pools Page allows you to add thread pools in addition to the native thread pool. Use these pools for a variety of purposes such as limiting a certain service to a specific number of concurrent threads.
The Thread Pools Page
The Thread Pools Page allows you to add thread pools. Use these pools for a variety of purposes such as limiting a certain service to a specific number of concurrent threads. To change thread pool settings once you've added the pool, edit obj.conf.If you are using Windows NT, you can also add native thread pools in addition to the generic thread pools you can add with this page.
Name of Pool. Specifies the thread pool you are adding.
Minimum Threads. Determines the minimum number of threads in the pool.
Maximum Threads. Determines the maximum number of threads in the pool. If you specify 1, you emulate single-threaded behavior.
Queue Size. Determines the number of threads that can wait in the queue for the thread pool. If all threads in the pool are busy, the next request-handling thread that tries to get in the queue is rejected, with the result that it returns a busy response to the client. It is then free to handle another incoming request instead of being tied up waiting in the queue.
Stack Size (bytes). Determines the stack size of each thread in the pool. The minimum value you can enter is 65536. Entering 0 specifies the default stack size for the operating system.
OK. Saves your entries. You must click Save and Apply for your changes to take effect.
Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.
Current Thread Pools. Lists the current thread pools. To modify a thread pool, click Edit in the thread pool row. To delete a thread pool, click Remove in the thread pool row.
The Global MIME Types Page
MIME (Multi-purpose Internet Mail Extension) types control what types of multimedia files your mail system supports. MIME types also specify what file extensions belong to certain server file types, for example to designate what files are CGI programs. For more information on using file extensions with programs, see Installing CGI Programs.The Global MIME Types page allows you to map a file extension with a file type.For more information, see Specifying a Default MIME Type.
The following elements are displayed:
New Type. Adds a new MIME type. Fill in the following fields:
Category. Specifies the category of the MIME type. Choose from the following options:
type. MIME standard set of identifiers for content. MIME is a standard identifier that defines the type of media content and its format so that the heterogeneous client or server applications can interpret the multimedia content that they exchange. The MIME types file contains the default MIME types definitions that will be used for the server.
Content-Type. Specifies the nature of the file. For example, the file could be text, video, and so forth. The receiving client (such as Netscape Navigator) uses the header string to determine how to handle the file, (for example, by starting a separate application or using a plug-in application).enc. A response header field sent with compressed documents in addition to a document's MIME type. It indicates to the client browser the response data has been compressed or modified by a filter, so that the client can decompress the response data before presenting it to the user.
lang. A language encoding header field specifying the language of the document.
File Suffix. Specifies all the file suffixes that will be associated with the content type. To specify more than one extension, separate the entries with a comma. File extensions must be unique; do not map one file extension to two MIME types.
Edit. Allows you to edit the category, content type, or file suffix of the MIME type.
The Network Settings Page
The Network Settings page allows you to configure the server's network setting.For more information, see Configuring Network Settings.
The following elements are displayed:
Server Location (Unix/Linux). Displays the absolute path where the server's scripts, icons, and configuration files are stored.
Server User (Unix/Linux). Specifies the user name under which the server runs. The server user should have restricted access to your system resources. You can often use a user named nobody in this situation. On some systems, however, nobody is not a valid user name. You may not want to give the user nobody group access to all files. If you do not use nobody, create a new Unix/Linux user, such as adm, to be the server user.
For Windows NT, you use the Services item in the control panel to change the server user. You can make the server a system account.
Server Name. Specifies the fully qualified host name of this server (for example, www.mozilla.com).
Server Port. Specifies the TCP port number to which the server listens to requests. The port number can be any port from 1 to 65535.
Bind To Address. Specifies the IP address of the server.
MTAHost. Specifies the name of the mail server that this server uses to send mail.
OK. Saves your entries. You must click Apply on the top right side of the page for your changes to take effect. If you do not click Apply after you update information, your changes are retained so that you can view and edit it, even though the changes have not taken effect.
Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.
The Custom Error Responses Page
A custom error response sends a detailed message to clients when they encounter errors from your server. The Custom Error Responses page allows you to specify a file to send or a CGI program to run for each HTTP code.For more information, see Customizing Error Responses.
The following elements are displayed:
Editing. Specifies a resource for which you want to customize error responses. If you choose a directory, the customized error responses apply only when the server receives a URL for that directory or any file in that directory.
Browse. Allows you to browse the file system and choose a portion of the server.
Wildcard. Specifies a wildcard pattern to edit. For information on using wildcard patterns, see Wildcards Used in the Resource Picker.
Error Code. Displays the following error codes which you can customize:
Unauthorized. Specifies the file to display when users without access permissions try to access a document on the server that is protected by access control. You might send information on how they can get access.
File. Specifies the files that contain your customized error messages.Forbidden. Specifies the file to display when the server does not have file system permissions to read something, or if the server is not permitted to follow symbolic links.
Not Found. Specifies the file to display when the server cannot find a document or when it has been instructed to deny the existence of a document.
Server Error. Specifies the file to display when the server is not configured properly or when a catastrophic error occurs, such as the system running out of memory or producing a core dump.
To remove a customization for an error code, delete the filename from the File field.
CGI. Specifies that the file that you specified is a CGI script, and specifies the absolute path to the file or CGI script that you want to return for that error code.
OK. Saves your entries. You must click Apply on the top right side of the page for your changes to take effect. If you do not click Apply after you update information, your changes are retained so that you can view and edit it, even though the changes have not taken effect.
Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.
The Dynamic Configuration Files Page
Server content is seldom managed entirely by one person. You may need to allow end users to access a subset of configuration options so that they can configure what they need to, without giving them access to iPlanet Web Server. The subset of configuration options are stored in dynamic configuration files. Two types of dynamic configuration files are supported by iPlanet Web Server: .htaccess and .nsconfig. The Dynamic Configuration Files page allows you to specify basic configuration for dynamic configuration files.For more information, see Working with Dynamic Configuration Files.
The following elements are displayed:
Editing. Specifies a resource for which you want to customize error responses. If you choose a directory, the customized error responses apply only when the server receives a URL for that directory or any file in that directory.
Browse. Allows you to browse the files in your server.
Wildcard. Specifies a wildcard pattern to edit. For information on using wildcard patterns, see Wildcards Used in the Resource Picker.
Status message: Dynamic Configuration Is/Is Not Enabled for This Resource. Specifies whether dynamic configuration is enabled. You can enable .nsconfig files in iPlanet Web Server, but you have to manually enable .htaccess files.
Base Directory from URL. Specifies the location where the server starts its search for configuration files from the document root.
Base Directory. Specifies the location where the server starts its search for configuration files from the file system directory.
File Name. Specifies the name of the configuration file to search for within the base directory.
Search. Searches for the file name in either subdirectories or in the base directory.
Disabled Types. Specifies the file types to disable in the directories where dynamic configuration is enabled.
OK. Saves your entries. You must click Apply on the top right side of the page for your changes to take effect. If you do not click Apply after you update information, your changes are retained so that you can view and edit it, even though the changes have not taken effect.
Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.
The Access Control List Management Page
The Access Control List page allows you to create and manage access control lists (ACLs). ACLs allow you to control which clients can access your server. ACLs can screen out certain users, groups, or hosts to either allow or deny access to part of your server, and set up authentication so that only valid users and groups can access part of the server.For more information, see the following sections:
What Is Access Control?
The following elements are displayed:
Pick a Resource
Displays all the resources in the server's document root that use ACLs to restrict access. An ACL can be any uniform resource identifier (URI). The URI in the ACLs list may be a directory, file name, or an alias to a resource such as a CGI script or servlet.Editing. Specifies a resource to manage.
Browse. Specifies only a portion of the server.
Wildcard. Specifies a wildcard pattern to edit. For information on using wildcard patterns, see Wildcards Used in the Resource Picker.
Edit Access Control. Edits the access control list for the selected resource.
Pick an Existing ACL
Specifies an ACL from the list of all the ACLs enabled for the server. Even if an ACL exists, if you have not enabled it, it will not appear in this list.Editing. Specifies a resource to manage.
Edit Access Control. Edits the selected access control list.
Type in the ACL Name
Creates an ACL. Use this option only if you're familiar with ACL files and the obj.conf configuration file—you'll need to manually edit obj.conf if you want to apply named ACLs to resources.Editing. Specifies a resource to manage.
Edit Access Control. Edits the selected access control list.
The Edit Access Control Page
The Edit Access Control page is divided into two frames that set the access control rules. If the resource you chose already has access control, the rules will appear in the top frame.For more information, see Restricting Access to Your Web Site and ACL File Syntax.
Upper Frame
The upper frame displays access control rules representing each configurable setting as a link. When you click on a link, the page divides into two frames, and you can use the Lower Frame to set the access control rules. The following elements are displayed in the upper frame:Action. Specifies whether to deny or allow access to the users, groups, or hosts.
Users/Groups. Allows you to specify user and group authentication when you click "anyone." The bottom frame allows you to configure User-Group authentication. By default, no users or groups outside of the group admin can access Administration Server resources. For more information, see Specifying Users and Groups.
From Host. Allows you to specify the computers you want to include in the rule when you click "anyplace". In the bottom frame, you can enter wildcard patterns of host names or IP addresses to allow or deny. For more information, see Specifying Host Names and IP Addresses.
Rights. Allows you to specify access rights to files and directories on your web site. In addition to allowing or denying all access rights, you can specify a rule that allows or denies partial access rights. For example, you can give people read-only access rights to your files, so they can view the information but not change the files.
Extra. Allows you to specify a customized ACL entry. This is useful if you use the access control API to customize ACLs. For more information, see Writing Customized Expressions.
Continue. Specifies that the next line in the access control rule chain is evaluated before the server determines if the user is allowed access. When creating multiple lines in an access control entry, it's best to work from the most general restrictions to the most specific ones.
Trash Can Icon. Deletes the corresponding line from the access control rules.
Access Control Is On. Specifies whether access control is enabled.
New Line. Adds a default ACL rule to the bottom row of the table. You can use the up and down arrows in the left column to move the rule.
Response when Denied. Specifies the response a user sees when denied access. You can vary the message for each access control object. By default, the user is sent a message saying that the file was not found (the HTTP error code 404 Not Found is also sent).
Revert. Erases your changes and resets the elements in the page to the values they contained before your changes.
Help. Displays the online help.
Lower Frame
The lower frame allows you to configure access control rules for the ACL in the Upper Frame. The following elements are displayed in the lower frame:
Allow/Deny
Allow. Allows the user, group, or host access.Deny. Denies the user, group, or host access.
Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.
Help. Displays the online help.
User/Group
Anyone (No Authentication). Allows everyone access to the resource. No authentication is required.Authenticated people only. Allows only authenticated users and groups to access the resource. Choose from the following options:
All in the Authentication Database. Allows all users and groups in the LDAP directory.
Prompt for Authentication. Allows you specify message text that appears in the authentication dialog box. You can use this text to describe what the user needs to enter. Depending on the operating system, the user will see about the first 40 characters of the prompt. Netscape Navigator and Netscape Communicator cache the username and password and associate them with the prompt text. This means that if the user accesses areas (files and directories) of the server that have the same prompt, the user will not have to retype usernames and passwords. Conversely, if you want to force users to reauthenticate for various areas, you must change the prompt for the ACL on that resource.Only the Following People. Allows only the users and groups specified. Click List under Group or User to list or search for groups and users in the LDAP directory.
Authentication Methods. Specifies the method the server uses when getting authentication information from the client.
Default uses the default method you specify in the obj.conf file, or "Basic" if there is no setting in obj.conf. If you check Default, the ACL rule doesn't specify a method in the ACL file. Default is the best choice because you can easily change the methods for all ACLs by editing one line in the obj.conf file.
Authentication Database. Lets you select a database that the server uses to authenticate users. The default setting means the server looks for users and groups in an LDAP directory. However, you can configure individual ACLs to use different databases. You can specify different databases and LDAP directories in the file server_root/userdb/dbswitch.conf. Then, you can choose the database you want to use in the ACL by selecting it in the drop-down list. If you use the access control API to use a custom database (for example, to use an Oracle or Informix database), you can type the name of the database in the "Other" field in the User/Group window.Basic uses the HTTP method to get authentication information from the client. The username and password are only encrypted if encryption is turned on for the server.
SSL uses the client certificate to authenticate the user. If you use this method, SSL must be turned on for the server. If you have encryption on, you can combine Basic and SSL methods.
Other uses a custom method you create using the access control API.
Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.
Help. Displays the online help.
From Host
Any place. Allows any machine access to the resource.Only from. Allows only the specified host names or IP address access to the resource. You specify this restriction by using wildcard patterns that match the machines' host names or IP addresses. For example, to allow or deny all computers in a specific domain, you would enter a wildcard pattern that matches all hosts from that domain, such as *.iplanet.com.
Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.
Help. Displays the online help.
Rights
All Access Rights. Allows the user, group, or host all access rights: read, write, execute, delete, list, and info.Only the Following Rights. Allows the user, group, or host only the selected access rights. Choose from the following:
Read. Allows a user view a file. Read access right includes the HTTP methods GET, HEAD, POST, and INDEX.
Update. Saves your entries.Write. Allows a user change or delete a file. Write access right includes the HTTP methods PUT, DELETE, MKDIR, RMDIR, and MOVE. To delete a file, a user must have both write and delete privileges.
Execute. Allows a user to execute server-side applications, such as CGI programs and Java applets.
Delete. Allows a user who also has write privileges to delete a file or directory.
List. Allows a user to get directory information. The user can get a list of the files in that directory. This applies to directories that do not contain an index.html file.
Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.
Help. Displays the online help.
Customized Expressions
Customize Expressions. Allows you to enter custom expressions for an ACL in the text box. You can use this feature if you are familiar with the syntax and structure of ACL files. For more information on customized expressions, see Writing Customized Expressions, and ACL File Syntax.Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.
Help. Displays the online help.
Access Deny Response
Respond with the Default File (Redirection Off). Displays the HTTP error code 404 Not Found error when the file being requested is not found.Respond with the Following URL: (Redirection On). Specifies a URL or the absolute path to a text or HTML file in your server's document root that you want to send to users when they are denied access. Be sure the server has read access to this file on your system—it's a good idea to have the file in a directory under the server root.
The Encryption On/Off Page
If you are accessing this page from the Administration Server, see The Encryption On/Off Page in the Administration Server section.The Encryption On/Off page allows you to activate or deactivate SSL for the server.
For more information, see the following sections:
About iPlanet Web Server Security
The following elements are displayed:Encryption. Specifies whether encryption is activated for the server.
Port Number. Specifies the port number that the server runs on. Port numbers can be any number from 1 to 65535; however, the standard secure server port is 443.
OK. Saves your entries. You must click Apply on the top right side of the page for your changes to take effect. If you do not click Apply after you update information, your changes are retained so that you can view and edit it, even though the changes have not taken effect.
Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.
The Encryption Preferences Page
If you are accessing this page from the Administration Server, see The Encryption Preferences Page in the Administration Server section.The Encryption Preferences page allows you to set encryption preferences for your server if SSL is activated. You can specify SSL version, whether your server will require client certificates, and which ciphers your server is able to use.
The following elements are displayed:
Allow. Specifies which SSL versions the server allows. Choose one or both of the following:
SSL version 2. An older version of SSL that clients may use.
Require Client Certificates (Regardless of Access Control). Specifies whether the server should refuse any client who does not have a client certificate from a trusted CA.SSL version 3. A more recent and more secure version of SSL.
SSL 2.0 Ciphers. Specifies which algorithms for the 2.0 version of SSL to use in encryption.
SSL 3.0 Ciphers. Specifies which algorithms for the 3.0 version of SSL to use in encryption.
OK. Saves your entries. You must click Apply on the top right side of the page for your changes to take effect. If you do not click Apply after you update information, your changes are retained so that you can view and edit it, even though the changes have not taken effect.
Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.
The Enforce Strong Security Requirements Page
The Enforce Strong Security Requirements page allows you to enforce stronger security requirements.In the domestic version, the Stronger Ciphers option presents a choice of 56-bit secret keysize restriction, or no restriction. A filename to be served when the restriction is not met can be specified. If no filename is specified, iPlanet Web Server returns a "Forbidden" status.
If you select a restriction that is not consistent with the current cipher settings under Security Preferences, iPlanet Web Server displays a popup dialog that warns that you need to enable ciphers with larger secret keysizes.
For more information, see the following sections:
Specifying Ciphers
The following elements are displayed:Editing. Specifies the resource for which you want to require the secret key size.
Browse. Allows you to browse your file system.
Wildcard. Specifies a wildcard pattern. For information on using wildcard patterns, see Wildcards Used in the Resource Picker.
Require 56 Bit or Larger Secret Key Size for Access. Specifies that the client must have a minimum of 58 bits in the secret key in order to successfully gain access to the server.
No Restrictions on Secret Key Size. Specifies that there are no minimum requirements on the secret key size.
Reject Access with File. Specifies a path to the file that will be served when the secret key size restriction is not met. If no file is specified, the server returns a "Forbidden" error.
OK. Saves your entries. You must click Apply on the top right side of the page for your changes to take effect. If you do not click Apply after you update information, your changes are retained so that you can view and edit it, even though the changes have not taken effect.
Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.
The Programs Tab
The Programs tab allows you to run server-side applications. The Programs tab contains the following pages:
The CGI Directory Page
The WINCGI Directory Page (Windows NT)
The CGI Directory Page
The CGI Directory page allows you to specify the directory where CGI programs will be stored.For more information, see Installing CGI Programs.
The following elements are displayed:
URL Prefix. Specifies the URL prefix for the CGI directory. The text you type in this field appears as the directory for the CGI programs in URLs.
For example, if you type cgi-bin as the URL prefix, then all URLs to these CGI programs have the following structure:
http://yourserver.domain.com/cgi-bin/program-name
Note The URL prefix you specify can be different from the real CGI directory you specify in the CGI directory field.
CGI Directory. Specifies the absolute path of the CGI directory. This this directory does not have to be under your document root.
OK. Saves your entries. You must click Apply on the top right side of the page for your changes to take effect. If you do not click Apply after you update information, your changes are retained so that you can view and edit it, even though the changes have not taken effect.
Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.
Current CGI Directories. Lists all CGI directories currently defined for the server. To modify a CGI directory, click Edit in the directory row. To delete a CGI directory, click Remove in the directory row.
The CGI as a File Type Page
The CGI as a File Type page allows you to associate a file extension with the shell CGI feature. This is different from creating an association in Windows NT.For more information, see Installing CGI Programs.
The following elements are displayed:
Editing. Specifies the resource you want to specify as a shell CGI type. If you choose a directory, all the files in that directory will be treated as a shell CGI script.
Browse. Allows you to browse your file system.
Wildcard. Specifies a wildcard pattern. For information on using wildcard patterns, see Wildcards Used in the Resource Picker.
Activate CGI as a File Type. Activates CGI as a file type and associates a file extension with the shell CGI feature in the server, such as an association for files with the .pl extension. When the server gets a request for a file with that extension, the server knows to treat the file as a shell CGI file by calling the executable associated in Windows NT with that file extension. If you activated CGI, WinCGI, and shell CGI file types, you must specify a unique suffix for each type of CGI. For example, you cannot use the suffix .exe for both a CGI program and a shell CGI program.
OK. Saves your entries. You must click Apply on the top right side of the page for your changes to take effect. If you do not click Apply after you update information, your changes are retained so that you can view and edit it, even though the changes have not taken effect.
Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.
The Query Handler Page
A query handler processes text sent to it via the ISINDEX tag in an HTML file. ISINDEX is similar to a text field on a page in that it creates a text field in the HTML page that can accept typed input. Unlike the information in a page text field, however, the information in the ISINDEX field is immediately submitted when the user presses Return. When you specify your default query handler, you tell the server to which program to direct the input. For an in-depth discussion of the ISINDEX tag, see an HTML reference manual.The Query Handler page allows you to specify a default query handler CGI program.
For more information, see Using the Query Handler.
The following elements are displayed:
Editing. Specifies a resource to edit. If you choose a directory, the query handler you specify runs only when the server receives a URL for that directory or any file in that directory.
Browse. Allows you to browse your file system.
Wildcard. Specifies a wildcard pattern. For information on using wildcard patterns, see Wildcards Used in the Resource Picker.
Default Query Handler. Specifies the absolute path for the CGI program used as the default for the resource you chose.
OK. Saves your entries. You must click Apply on the top right side of the page for your changes to take effect. If you do not click Apply after you update information, your changes are retained so that you can view and edit it, even though the changes have not taken effect.
Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.
The WINCGI Directory Page (Windows NT)
The WINCGI Directory page allows you to create a directory that contains only Windows CGI programs.For more information, see the following sections:
Installing Windows NT CGI Programs
The following elements are displayed:URL Prefix. Specifies the URL prefix you want to use for the WINCGI directory. That is, the text you type appears as the directory for the Windows CGI programs in URLs.
For example, if you type wcgi-programs as the URL prefix, then all URLs to these Windows CGI programs have the following structure:
The URL prefix can be different from the real Windows CGI directory you specify in the WINCGI Directory field.
- http://yourserver.domain.com/wcgi-programs/program-name
WINCGI directory. Specifies the location of the CGI directory as an absolute path. This directory does not have to be under your document root.
Enable Script Tracing. Specifies whether your server will use script tracing. CGI parameters are passed from the server to Windows CGI programs through files, which the server normally deletes after the Windows CGI program finishes execution. If you enable script tracing, these files are retained in a /temp directory or wherever the environment variables TMP and TEMP are pointing. Also, any window that the Windows CGI program brings up is shown when script tracing is enabled.
OK. Saves your entries. You must click Apply on the top right side of the page for your changes to take effect. If you do not click Apply after you update information, your changes are retained so that you can view and edit it, even though the changes have not taken effect.
Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.
The Shell CGI Directory Page (Windows NT)
The Shell CGI Directory page allows you to create a directory in your server's document root that contains only shell CGI files.For more information, see Installing Shell CGI Programs for Windows NT.
The following elements are displayed:
URL Prefix. Specifies the URL prefix associated with your shell CGI directory. For example, suppose you store all shell CGI files in a directory called C:/docs/programs/cgi/shell-cgi, but you want users to see the directory as http://www.yourserver.com/shell/. In this case, you would type shell as the URL prefix.
Shell CGI directory. Specifies the absolute path to the directory you created to store the shell CGI files. Make sure that any files in the shell CGI directory also have file associations set in Windows NT. The server returns an error if it attempts to run a file that has no file-extension association.
OK. Saves your entries. You must click Apply on the top right side of the page for your changes to take effect. If you do not click Apply after you update information, your changes are retained so that you can view and edit it, even though the changes have not taken effect.
Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.
The Servlets Tab
The Servlets tab allows you to configure the servlet engine. The Servlets tab contains the following pages:
The Enable Servlets/JSP Page
The Configure Global Attributes for Servlets Page
The Configure Servlet Attributes Page
The Configure Servlet Virtual Path Translation Page
The Enable Servlets/JSP Page
The Enable Servlets page allows you to enable and disable servlets and Java Server Pages (JSP).For more information, see Enabling Servlets and JSP.
The following elements are displayed:
Activate the Servlet Engine. Specifies whether the server can serve servlets. If the servlet engine is not activated, the server cannot serve servlets. Disabling the servlet engine also disables Java Server Pages (JSP), so the next time you enable the servlet engine you must enable JSP again if desired.
Servlet Thread Pool. Allows you to specify a thread pool for servlets. For information about how to define thread pools, see The Native Thread Pool Page (NT), The Thread Pools Page, or The Thread Pools Page.
Enable JSP. Specifies whether iPlanet Web Server will parse and display Java Server Pages (JSP). JSP files must have a .jsp extension. If JSP is not enabled, accessing a .jsp file generates a server error.
OK. Saves your entries. You must click Apply on the top right side of the page for your changes to take effect. If you do not click Apply after you update information, your changes are retained so that you can view and edit it, even though the changes have not taken effect.
Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.
The Servlet Directory Page
The Servlet Directory page allows you to specify the directories where servlets are located.For more information, see Specifying Servlet Directories.
The following elements are displayed:
URL Prefix. Specifies the prefix used in URLs for accessing the servlet directory. For example, if you want the URL http://server_name/plans to map to the directory D:/netscape/server4/docs/plans then enter plans in this field.
Servlet Directory. Specifies the absolute path to the directory to be registered as a servlet directory. Servlets in this directory are invoked by URLs that use the URL prefix specified in the previous field. iPlanet Web Server treats all files in these directories as servlets.
OK. Saves your entries. You must click Apply on the top right side of the page for your changes to take effect. If you do not click Apply after you update information, your changes are retained so that you can view and edit it, even though the changes have not taken effect.
Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.
Current Servlet Directories. Lists the current servlet directories. To modify a servlet directory, click Edit in the servlet directory row. To delete a servlet directory, click Remove in the servlet directory row.
The Legacy JSP Directory Page
The Legacy JSP Directory page allows you to specify the directories where version 0.92 JSPs are located.The following elements are displayed:
URL Prefix. Specifies the prefix used in URLs for accessing the legacy JSP directory. For example, if you want the URL http://server_name/plans to map to the directory D:/netscape/server4/docs/plans then enter plans in this field.
Legacy JSP Directory. Specifies the absolute path to the directory to be registered as a legacy JSP directory. JSPs in this directory are invoked by URLs that use the URL prefix specified in the previous field. iPlanet Web Server treats all files in these directories having the .jsp extension as version 0.92 JSPs.
OK. Saves your entries. You must click Apply on the top right side of the page for your changes to take effect. If you do not click Apply after you update information, your changes are retained so that you can view and edit it, even though the changes have not taken effect.
Reset.Erases your changes and resets the elements in the page to the values they contained before your changes.
Current JSP Directories. Lists the current legacy JSP directories. To modify a JSP directory, click Edit in the legacy JSP directory row. To delete a JSP directory, click Remove in the legacy JSP directory row.
The Configure Global Attributes for Servlets Page
The General Attributes for Servlets page allows you to specify general servlet properties.For more information, see Configuring Global Attributes.
The following elements are displayed:
Startup Servlets. Specifies the servlets that will be loaded upon starting the server. Do not include the .class extension.
Session Manager. Specifies the session manager class value.
Reload Interval. Specifies the interval (in seconds) in which the servlets and JSP are reloaded. If the servlet class file changes, a servlet instance (reflecting the changes) can be reloaded. Enter an integer value between 0 and 600 inclusive.
OK. Saves your entries. You must click Apply on the top right side of the page for your changes to take effect. If you do not click Apply after you update information, your changes are retained so that you can view and edit it, even though the changes have not taken effect.
Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.
The Configure Servlet Attributes Page
The Configure Servlet Attributes page allows you to add servlets to the servlets.properties file and to specify input parameters, class path, and virtual path translation for existing servlets. You can set up virtual path translations for servlets regardless of whether they reside in registered servlet directories. When you add a servlet through this interface, the servlet is automatically added to the servlets.properties file in iPlanet Web Server's config directory.For more information, see Configuring Servlet Attributes.
The following elements are displayed:
Choose Servlet. Specifies the servlet to edit. Upon choosing the servlet from this drop-down list, the servlet's information is displayed in the lower portion of this page (Ignore this field if you are adding a new virtual path entry).
Note To add a servlet to the servlets.properties file, fill out the following fields in the lower portion of the page.
Servlet Name. Specifies an identifier for the servlet. This identifier is used internally by iPlanet Web Server; it is not used in the URL for accessing the servlet. This identifier can be the same name or a different name than the servlet class name.
Servlet Code (class name). Specifies the name of the servlet's main class file. The .class extension is not required. Do not specify any directories in this field.
Servlet Classpath. Specifies the absolute path or URL to the classpath for the servlet. The classpath can point anywhere in the file system. The servlet classpath may contain a directory, a .jar or .zip file, or a URL to a directory (You cannot specify a URL as a classpath for a .zip or .jar file.). If the servlet classpath is not a registered servlet directory, you must provide a servlet virtual path translation (in the The Configure Servlet Virtual Path Translation Page) to make the servlet accessible to browsers.
Servlet Args. Lists optional initial arguments passed to the servlet. Input must be in the format name=value [,name=value], for example, name1=arg1, name2=arg2.
OK. Saves your entries. You must click Apply on the top right side of the page for your changes to take effect. If you do not click Apply after you update information, your changes are retained so that you can view and edit it, even though the changes have not taken effect.
Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.
The Configure Servlet Virtual Path Translation Page
The Configure Servlet Virtual Path Translation page allows you to add and edit virtual paths for your servlets. For example, you can set a virtual path for the servlet named servplan1 in the docs/products/mrktplans directory to allow users to invoke this servlet by using the URL http://server_name/plans/plan1.You can specify virtual paths only for servlets that are listed in the servlets.properties file. (To add a servlet to this file, use the The Configure Servlet Attributes Page.)
For more information, see Configuring Servlet Virtual Path Translations.
The following elements are displayed:
Choose Virtual Path Entry. Specifies a virtual path to modify. Upon choosing the servlet from this drop-down list, the virtual path information will be displayed in the lower portion of this page (Ignore this field if you are adding a new virtual path entry).
Virtual Path. Specifies a new virtual path to add, or an existing one to modify. If you want to add a new path, you can overwrite the text (if any) in this field. If you want to modify the virtual path, choose the path from the list in Choose Virtual Path Entry above this field.
Note To add a virtual path, fill out the following fields in the lower portion of the page.
Servlet. Specifies an identifier for the servlet, as entered in Configuring Servlet Attributes. You can create the servlet identifier in this field before specifying it in the The Configure Servlet Attributes Page, but you must specify it in The Configure Servlet Attributes Page before the virtual path will work.
To remove an existing translation, select the name of the virtual path in the Choose Virtual Path Entry menu, then click Remove.
OK. Saves your entries. You must click Apply on the top right side of the page for your changes to take effect. If you do not click Apply after you update information, your changes are retained so that you can view and edit it, even though the changes have not taken effect.
Remove. Deletes the selected virtual path from the rules.properties file.
The Configure JVM Attributes Page
The Configure JVM Attributes page allows you to set parameters for the Java virtual machine (JVM).For more information, see Configuring JVM Attributes.
The following elements are displayed:
Option. Specifies any options allowed by the vendor's JVM.
Profiler. Specifies a value for the optimizer. Enter "optimizeit" if you are using the Optimizeit! 3.0 profiler from Intuitive Systems.
OPTITDIR. Specifies the absolute path for the directory where Optimizeit! resides, for example, D:/App/IntuitiveSystems/OptimizeIt30D if you are using the Optimizeit! 3.0 profiler from Intuitive Systems.
Minimum Heap Size. Specifies the minimum heap size for the interpreter.
Maximum Heap Size. Specifies the maximum heap size for the interpreter. This setting has the same fuctionality as the command-line option -mx in Java.
Compiler. Specifies whether the Just-in-time (JIT) complier is on or off.
Classpath. Specifies the Java classpath where the classes for the servlet engine are located and any additional classpath information needed by servlets or JSP. Each path must be separated by semicolons (for example, /directory/directory;/directory/directory). For example, if a JSP uses a bean that is packaged in a JAR, add the JAR path to the classpath. You can add values to an existing classpath, but do not delete values from a classpath.
Enable Class GC. Specifies whether or not to enable class garbage collection.
Verbose Mode. Specifies whether the logging collection (if enabled) will be in verbose mode.
Enable Debug. Enables remote debugging.
OK. Saves your entries. You must click Apply on the top right side of the page for your changes to take effect. If you do not click Apply after you update information, your changes are retained so that you can view and edit it, even though the changes have not taken effect.
Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.
The Delete Version Files Page
The Delete Version Files page allows you to delete the files that contain the version number for the Java server pages class cache and session data cache. When the server detects these files during start-up, it checks the version and if the current version is lower then it is supposed to be, it deletes the current directories and creates new ones.For more information, see Deleting Version Files.
The following elements are displayed:
Delete the SessionData Version File. Deletes the version file for the session data. When you apply this change, the version file is deleted immediately. The next time the server starts up, it deletes the session data cache and recreates the version file. The next time the server serves a JSP or servlet while using the MMapSessionManager session manager, it recreates the session data cache.
Delete the ClassCache Version File. Deletes the class cache version files for JSP. when you apply this change, the version file is deleted immediately. The next time the server starts up, it deletes the JSP class cache and recreates the version file. The next time the server serves a JSP, it recreates the class cache if necessary.
OK. Saves your entries. You must click Apply on the top right side of the page for your changes to take effect. If you do not click Apply after you update information, your changes are retained so that you can view and edit it, even though the changes have not taken effect.
Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.
The Security Tab
The Server Manager Security tab contains the following pages:
The Create a Trust Database Page
The Request a Server Certificate Page
The Install a Server Certificate Page
The Create a Trust Database Page
If you are accessing this page from the Administration Server, see The Create a Trust Database Page in the Administration Server section.The Create a Trust Database page allows you to create a new trust database with the default CA settings and protect it with a password. The server can have only one trust database, so you can create a trust database only if one does not already exist. The trust database is created with the default CA entries which are configured so that they are not trusted CAs for client certificates. To configure the server to trust these CAs for use with client certificates, see The Manage Server Certificates Page (Administration Server).
For more information, see Creating a Certificate Trust Database.
The following elements are displayed:
Database Password. Specifies the certificate database password.
Password (again). Confirms the password specified in the Database Password field. If what you enter is different from what you entered in the Database Password field, you will be prompted to try again.
OK. Saves your entries. You must click Apply on the top right side of the page for your changes to take effect. If you do not click Apply after you update information, your changes are retained so that you can view and edit it, even though the changes have not taken effect.
Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.
The Request a Server Certificate Page
If you are accessing this page from the Administration Server, see The Request a Server Certificate Page in the Administration Server section.The Request a Server Certificate page allows you to add or renew a server certificate.
For more information, see Requesting a Certificate.
The following elements are displayed:
New certificate. Specifies that the certificate being requested is new.
Certificate renewal. Specifies that the certificate being requested is a renewal of an existing certificate.
List of available certificate authorities. Lists the certificate authorities from which you can get server certificates.
Submit to Certificate Authority via. Specifies the manner in which to submit the certificate request. If you wish to contact the certificate authority via email, select CA Email Address and enter the email address in the field.
Select the module to use with the Certificate. Specifies one of the following:
Cryptographic Module. Specifies the module to be used with the certificate.
Requestor name. Specifies the name under which the certificate will be issued.Key Pair File Password. Specifies the certificate database password.
Telephone number. Specifies the telephone number of the requestor.
Common name. Specifies the fully qualified hostname used in DNS lookups (for example, www.iplanet.com). This is the hostname in the URL that a browser uses to connect to your site. It is important that these two names are the same. Otherwise, a client is notified that the certificate name does not match the site name, which often makes uses doubt the authenticity of your certificate.
Email address. Specifies the business email address used for correspondence between you and the CA.
Organization. Specifies the official, legal name of your company, educational institution, organization, and so on. Most CAs require that you verify this information with legal documents (such as a copy of a business license).
Organizational Unit. Specifies a description of an organizational unit within your company. This field is optional.
Locality. Specifies a description of the city, principality, or country for the organization. This field is optional.
State or Province. Specifies the state or province in which the business is located.
Country. Specifies the two-character abbreviation of your country name (in ISO format). The country code for the United States is US.
OK. Saves your entries. You must click Apply on the top right side of the page for your changes to take effect. If you do not click Apply after you update information, your changes are retained so that you can view and edit it, even though the changes have not taken effect.
Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.
The Install a Server Certificate Page
If you are accessing this page from the Administration Server, see The Install a Server Certificate Page in the Administration Server section.You can install your own certificate to present to clients, or a CA's certificate for use in a certificate chain.
When you receive a certificate from the CA, it will be encrypted with your public key so that only you can decrypt it. The server will use the key-pair file password you specify to decrypt the certificate when you install it.
The Install a Server Certificate page allows you to install a certificate for a server.
For more information, see Installing and Managing Certificates and Certificate Lists.
The following elements are displayed:
Certificate For. Specifies where the certificate will be used. Select from the following options:
This Server. Specifies that the server will use the key-pair file password you specify to decrypt the certificate when you install it.
Select the module to use with the Certificate. Specifies one of the following:Server Certificate Chain. Allows the SSL connection to continue at the client's discretion when the client does not recognize the certificate's CA. Certificate chaining is the process of presenting your CA's certificate in addition to your own. If the client trusts the CA who issued the certificate to your CA, the transaction will continue. In this way, a chain of trust is created: the client trusts the second CA, who trusts the first CA, who trusts you. Therefore, the client trusts you.
Trusted Certificate Authority (CA). Accepts the certificate of a CA as a trusted CA for client authentication.
Cryptographic Module. Specifies the module to be used with the certificate.
Certificate Name. Specifies the common name of the certificate. Enter the certificate name only if it differs from the fully qualified hostname of your server used in DNS lookups (for example, www.iplanet.com).Key Pair File Password. Specifies the certificate database password.
Message is in this file. Specifies the file that contains the CA certificate.
Message text (with headers). Contains the content of the CA certificate. If you copy and paste the text, be sure to include the headers "Begin Certificate" and "End Certificate."
OK. Saves your entries. You must click Apply on the top right side of the page for your changes to take effect. If you do not click Apply after you update information, your changes are retained so that you can view and edit it, even though the changes have not taken effect.
Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.
The Change the Key Pair File Password Page
If you are accessing this page from the Administration Server, see The Change the Key Pair File Password Page in the Administration Server section.The Change the Key Pair File Password page allows you to change the password used to access your trust database.
For more information, see Secure Your Key-Pair File.
The following elements are displayed:
Old Password. Specifies the current key pair password.
New Password. Specifies the new key pair password.
Password (again). Confirms the password specified in the New Password field. If what you enter in this field is different from what you entered in the New Password field, you will be prompted to try again.
OK. Saves your entries. You must click Apply on the top right side of the page for your changes to take effect. If you do not click Apply after you update information, your changes are retained so that you can view and edit it, even though the changes have not taken effect.
Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.
The Manage Server Certificates Page
If you are accessing this page from the Administration Server, see The Manage Server Certificates Page (Administration Server) in the Administration Server section.The Manage Server Certificates page displays all the installed certificates associated with the server and allows you to manage the certificates.
The following elements are displayed:
Certificate Name. Specifies the name of the certificate authority.
Type. Specifies the type of certificate.
Expires (Time in UTC). Displays the date and time that the certificate expires. Once a certificate has expired, you must renew it to use it again.
The Status Tab
The Status Tab allows you to monitor your server's activity. The Status Tab contains the following pages:
The View Access Log Page
The View Access Log Page
If you are accessing this page from the Administration Server, see The View Access Log Page in the Administration Server section.The View Access Log page allows you to configure a customized view of the information about requests to the server and the responses from the server.
For more information, see the following sections:
About Log Files
The following elements are displayed:View this logfile. Specifies which log file to display. Active log files for resources and archived log files appear in the drop-down list.
Number of entries. Specifies the number of entries to retrieve (starting with the most recent).
Only show entries with. Specifies a string or a character to filter the log entries. Case is important; the case of the string or character specified in this field must match the case of the entry in the access log. For example, if you want to see only access log entries that contain POST, type "POST."
OK. Displays the log entries in the lower section of this page.
Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.
Last number accesses to access. Displays the access log entries with the parameters specified in the upper section of this page.
The View Error Log Page
If you are accessing this page from the Administration Server, see The View Error Log Page (Administration Server) in the Administration Server section.The View Error Log allows you to configure a customized view of the errors the server has encountered as well as the informational messages about the server, such as when the server was started and who has tried unsuccessfully to log in to the server.
For more information, see the following sections:
About Log Files
The following elements are displayed:Number of errors to view. Specifies the number of entries to retrieve (starting with the most recent).
Only show entries with. Specifies a string or a character to filter the log entries. Case is important; the case of the string or character specified in this field must match the case of the entry in the error log. For example, if you want to see only those error messages that contain warning, type "warning."
OK. Displays the log entries in the lower section of this page
Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.
Last number errors. Displays the error log entries with the parameters specified in the upper section of this page.
The Monitor Current Activity Page
If your server is running, the Monitor Current Activity page allows you to launch a program to monitor your server's current resource usage. This program will give you a feel for how many resources your server needs. If your server becomes sluggish at higher traffic levels, this will help you determine if you need to adjust your server configuration, or adjust the system's network kernel.For more information, see Monitoring the Server Using HTTP.
Displays the percentage of, the total count for, and the bar graph for the following Category information:
Bad requests. Total number of requests that are not processing successfully.
2xx. Total number of status codes ranging from 200 to 299 that the server is handling.
Help. Displays online help.3xx. Total number of status codes ranging from 300 to 399 that the server is handling.
4xx. Total number of status codes ranging from 400 to 499 that the server is handling.
5xx. Total number of status codes of 500 and higher that the server is handling.
xxx. Total number of 2xx, 3xx, 4xx, and 5xx status codes the server is handling minus timeouts and other errors that did return an HTTP status code
200. Total number of successful transactions the server is processing.
302 (Redirects) status codes. Total number of redirected URL status codes the server is processing because the original URL moved.
304 (Not Modified) status codes. Total number of requests for which the requesting client used a local copy of the requested document, rather than retrieving it from the server.
401. Total number of unauthorized requests the server is handling.
403. Total number of forbidden URL status codes the server is handling.
The Archive Log Files Page
The Archive Log page allows you to automatically rotate your log files at regular intervals. When you archive log files, the server renames the current log files and then creates new log files with the original names. You can archive or delete the old log files, which are saved as the original file name followed by the date and time the file was archived. For example, access might become access.24Apr-04AM.The Archive Log File page allows you to archive your log files immediately or specify days and times when archiving will take place.
For more information, see Archiving Log Files.
The following elements are displayed:
Internal daemon log rotation. Specifies whether to use iPlanet Web Server internal system daemon log settings for log rotation.
rotation start time. Specifies the time used as a basis to rotate log files and start a new log file. For example, if the rotation start time is 12:00 a.m., and the rotation interval is 1440 minutes (one day), a new log file will be created immediately upon save regardless of the present time and collect information until the rotation start time. The log file will rotate every day at 12:00 a.m., and the access log will be stamped at 12:00 a.m. and saved as access.24Apr-12AM. Likewise, if you set the interval at 240 minutes (4 hours), the 4 hour intervals begin at 12:00 a.m. such that the access log files will contain information gathered from 12:00 a.m. to 4:00 a.m., from 4:00 a.m. to 8:00 a.m., and so forth.
Cron based log rotation. Specifies whether to use the operating system's cron (or job scheduling) facility to schedule log archiving.rotation interval (minutes). Specifies the number of minutes until the next log rotation when a new log file is started. You must specify an interval of at least 30 minutes or more.
Note Before archiving the log files, you must shut down the The NS Cron Control Page (Unix/Linux) from the Administration Server.
Archive the log files now. Archives the log file that is currently being written to and restarts the server when you click Archive. Note that clicking "Archive the log files now" archives both the access and error logs.
OK. Saves your entries. You must click Apply on the top right side of the page for your changes to take effect. If you do not click Apply after you update information, your changes are retained so that you can view and edit it, even though the changes have not taken effect.rotate log at. Specifies the time and day of the week on which log archiving will occur. To select multiple times, hold the Control key when clicking on the time.
Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.
The Log Preferences Page
If you are accessing this page from the Administration Server, see The Logging Options Page in the Administration Server section.The Log Preferences page allows you to specify what information is recorded in your server's logs. Server log files can help you monitor your server's activity and troubleshoot problems.
For more information, see Setting Log Preferences.
The following elements are displayed:
Editing. Specifies a resource to which custom logging is applied. If you choose a directory, custom logging applies only when the server receives a URL for that directory or any file in that directory.
Browse. Allows you to browse your file system.
Wildcard. Specifies a wildcard pattern. For information on using wildcard patterns, see Wildcards Used in the Resource Picker.
Log client accesses. Specifies whether to include client accesses in your log files.
Log File. Specifies the absolute path for the access log file. As a default, the log files are kept in the logs directory in the server root. If you specify a partial path, the server assumes the path is relative to the logs directory in the server root.
Record. Specifies whether the server should record domain names or IP addresses of the systems accessing the server in the access log.
Format. Specifies which type of log file format to use in the access log. You can select from the following:
Use Common Logfile Format. Includes client's host name, authenticated user name, date and time of request, HTTP header, status code returned to the client, and content length of the document sent to the client, or
Custom Format. Allows you to create a customized format for your access log. For more information about the parameters you should use for your custom format, see theonline documentation web site at http://www.iplanet.com/docsOnly Log. Allows you to choose which information will be logged. You can choose from the following:
Client hostname. The hostname (or IP address if DNS is disabled) of the client requesting access.
Authenticate user name. If authentication was necessary, you can have the authenticated user name listed in the access log.
System date. The date and time of the client request.
Full request. The exact request the client made.
Status. The status code the server returned to the client.
Content length. The content length, in bytes, of the document sent to the client.
HTTP header, "referer". The referer specifies the page from which the client accessed the current page. For example, if a user was looking at the results from a text search query, the referer would be the page from which the user accessed the text search engine. Referers allow the server to create a list of backtracked links.
HTTP header, "user-agent". The user-agent information—which includes the type of browser the client is using, its version, and the operating system it's running on—comes from the User-agent field in the HTTP header information the client sends to the server.
Method. The HTTP request method used (GET, PUT, POST, etc.).
URI. Universal Resource Identifier. The location of a resource on the server. For example, for http://www.a.com:8080/special/docs, the URI is special/docs.
Query string of the URI. Anything after the question mark in a URI. For example, for
http://www.a.com:8080/special/docs?find_this, the query string of the URI is find_this.Protocol. The transport protocol and version used.
Do not log client accesses from. Specifies the hostnames and the IP addresses whose accesses will not be logged.
Hostnames. Specifies all hostnames from which your server will not log client accesses. You can use a wildcard pattern to signify which hosts to leave out of the access log. For example, use *.iplanet.com if you do not want to log accesses from the domain iplanet.com.
OK. Saves your entries. You must click Apply on the top right side of the page for your changes to take effect. If you do not click Apply after you update information, your changes are retained so that you can view and edit it, even though the changes have not taken effect.IP Addresses. Specifies all IP addresses from which your server will not log client accesses. You can use a wildcard pattern to signify which IP addresses to leave out of the access log. For example, use 208.12.* if you do not want to log access from IP addresses beginning with 208.12.
Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.
The Generate Report Page
The Generate Report page allows you to generate a report about a server's activity. Use the log analyzer to generate statistics about your server, such as a summary of activity, most commonly accessed URLs, times during the day when the server is accessed most frequently, and so on. You can also run the log analyzer from the Server Manager or the command line.
Note Before running the log analyzer, you should archive the server logs. For more information about archiving server logs, see Archiving Log Files.
For more information, see Running the Log Analyzer.
The following elements are displayed:
Server name. Specifies the name of the server for which to generate the report.
Output type. Specifies whether the report should be output to an HTML file or to a plain text (ASCII) file.
Log File. Specifies the log file or files to generate the report from. To select more than one file, hold the Control key when clicking on the file.
Output file. Specifies the absolute path to where the report should go. If you leave this field blank, the analyzer displays the results on the screen. For large log files, you should save the results to a file because displaying the output on the screen may take a long time.
Totals. Specifies whether you want to generate totals for statistics. Choose "Do not generate totals" if you do not want to generate totals for statistics. If you choose to generate totals, specify the items from the following list for which you would like to generate totals:
Total hits. Number of requests the server received since access logging was enabled.
General Statistics. Specifies whether to generate general statistics. Choose "Do not generate general statistics" if you do not want to generate general statistics. If you choose to generate statistics, choose from the following:304 (Not Modified) status codes. Number of times the requesting client used a local copy of the requested document, rather than retrieving it from the server.
302 (Redirects) status codes. Number of times the server redirected to a new URL because the original URL moved.
404 (Not Found) status codes. Number of times the server could not find the requested document or the server did not serve the document because the client was not an authorized user.
500 (Server Error) status codes. Number of times server-related error occurred.
Total unique URL's. Number of unique URLs accessed since access logging was enabled.
Total unique hosts. Number of unique client hosts who have accessed the server since access logging was enabled.
Total kilobytes transferred. Number of kilobytes the server transferred since access logging was enabled.
Find top number seconds of log. Generates statistics based on information from the most recent number of seconds.
Generate Lists. Specifies whether to generate lists. Choose Do not generate any list if you do not want to generate any lists. If you choose to generate lists, specify the items from the following list for which you would like to generate lists:Find top number minutes of log. Generates statistics based on information from the most recent number of minutes.
Find top number hours of log. Generates statistics based on information from the most recent number of hours.
Find number users (if logged). Generates statistics based on information from the number of user.
Find top number referers (if logged). Generates statistics based on information from the number of referers.
Find top number user agents (if logged). Generates statistics based on information from the number of agents.You can create predefined agents that run on the server and bring information back to you, such as email notification that a specific document has changed.
Find top number miscellaneous logged items (if logged). Generates statistics based on information from the number of user.
number most commonly accessed URL. Displays the most commonly accessed URLs or URLs that were accessed more than a specified number of times.
Output Order. Specifies the order of the output. Prioritize the following items from 1 to 3 in the order that you would like each section to appear in the report. If you chose to not generate any of them, the section will automatically be left out.URLs that were accessed more than number times. Displays the URL that were accessed more times than the number specified.
number hosts most often accessing your server. Displays the hosts most often accessing your server or hosts that have accessed your server more than a specified number of times
Hosts that accessed your server more than number times. Displays the hosts that accessed your server more times than the number specified.
OK. Saves your entries. You must click Apply on the top right side of the page for your changes to take effect. If you do not click Apply after you update information, your changes are retained so that you can view and edit it, even though the changes have not taken effect.
Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.
The Styles Tab
Configuration styles are an easy way to apply a set of options to specific files or directories that your server maintains. The Configuration Styles tab allows you to apply a set of options to specific files or directories that your server maintains. The Styles tab contains the following pages:
The Create a New Style Page
The Create a New Style Page
The Create a New Style page allows you to create a style.For more information, see Creating a Configuration Style.
The following elements are displayed:
Style Name. Specifies the name of the style you are creating.
OK. Creates a new style with the specified name and displays the Edit a Style page so that you can configure the new style. You must click Apply on the top right side of the page for your changes to take effect. If you do not click Apply after you update information, your changes are retained so that you can view and edit it, even though the changes have not taken effect.
Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.
The Remove a Style Page
The Remove a Style page allows you to remove a style.For more information, see Removing a Configuration Style.
The following elements are displayed:
Remove. Specifies the name of the style to delete.
OK. Saves your entries. You must click Apply on the top right side of the page for your changes to take effect. If you do not click Apply after you update information, your changes are retained so that you can view and edit it, even though the changes have not taken effect.
Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.
The Edit a Style Page
The Edit a Style page allows you to change the parameters of a style.For more information, see Editing a Configuration Style.
The following elements are displayed:
Style. Select a style from the drop-down list and Click Edit this style.
Edit. Click the configuration style category.
The Assign a Style Page
The Apply a Configuration Style page allows you to apply a configuration style to files or directories in your server. You can either specifically choose files and directories, or you can specify a wildcard pattern.For more information, see Assigning a Configuration Style.
The following elements are displayed:
URL prefix wildcard. Specifies files or directories, or the wildcard pattern (for example, * gif). If you enter /* after the directory, the configuration style will be applied to all the directory's contents.
Style. Specifies the configuration style you want to apply. The None configuration style can be applied to files or directories to remove any configuration style previously applied to the resource.
OK. Saves your entries. You must click Apply on the top right side of the page for your changes to take effect. If you do not click Apply after you update information, your changes are retained so that you can view and edit it, even though the changes have not taken effect.
Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.
The List Assignments Page
After you have created configuration styles and applied them to files or directories, you can list all the configuration styles and the files or directories to which they are applied. The List Assignments page displays all the configuration styles applied to the server resource.For more information, see Listing Configuration Style Assignments.
The following elements are displayed:
Style Assignments. Lists all configuration style assignments
Pattern. Displays files or directories, or the wildcard pattern, this style is applied to.
Style. Displays the name of the configuration style.
Edit this style. Click this link to edit or remove the configuration style assignment. Clicking this link takes you to the The Assign a Style Page. A Remove this Style link appears at the top of the page.
The Content Management Tab
The Content Management tab allows you to manage your server's content. The Content Management tab contains the following pages:
The Primary Document Directory Page
The Additional Document Directories Page
The User Document Directories Page (Unix/Linux)
The Hardware Virtual Servers Page
The Software Virtual Servers Page
The Primary Document Directory Page
You use the Primary Document Directory page to change the primary document directory, which is the central directory where you store all the files you want to make available to remote clients.For more information, see Changing the Primary Document Directory.
The following elements are displayed:
Primary directory. Specifies the absolute path of the server's primary document directory.
OK. Saves your entries. You must click Apply on the top right side of the page for your changes to take effect. If you do not click Apply after you update information, your changes are retained so that you can view and edit it, even though the changes have not taken effect.
Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.
The Additional Document Directories Page
The Additional Document Directories page allows you to add document directories to your web server and to map URLs to document directories. You use the Additional Document Directories page to create additional document directories for the documents on your web server.For more information, see Setting Additional Document Directories.
The following elements are displayed:
URL prefix. Specifies the URL prefix you want to map. For example, a mapped URL could be http://www.mozilla.com/marketing/index.html where marketing/ is the prefix you specify. Enter a nickname that maps the URL to the additional document directory you want to define such as the word, plans.
Map To Directory. Specifies the absolute path of the directory you want the URL prefix to map to, for example,
C:\Netscape\marketing\pubdocs\index.html.Apply Style. Specifies a configuration style to apply to the additional directory's configuration.
OK. Saves your entries. You must click Apply on the top right side of the page for your changes to take effect. If you do not click Apply after you update information, your changes are retained so that you can view and edit it, even though the changes have not taken effect.
Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.
Current Additional Directories. Displays all additional document directories on your server. To modify a directory's mapping, click Edit in the directory row. To delete a directory's mapping, click Remove in the directory row.
The User Document Directories Page (Unix/Linux)
The User Document Directories page allows you to configure public information directories that let all the users on your server create home pages and other documents without your intervention.For more information, see Customizing User Public Information Directories (Unix/Linux).
The following elements are displayed:
User URL Prefix. Specifies the URL prefix for the user directory (~ is the default).
Subdirectory. Specifies the user's subdirectory (public_html is the default).
Password File. Specifies whether you want the server to use the system's password file or a user file you have created to look up users.
System file. Specifies the path to the system's password file.
Apply Style. Specifies the configuration style to apply to the additional directory's configuration.This file. Specifies the absolute path to user file.
Load entire database on start-up. Specifies whether you want to load the entire password file on start-up.
OK. Saves your entries. You must click Apply on the top right side of the page for your changes to take effect. If you do not click Apply after you update information, your changes are retained so that you can view and edit it, even though the changes have not taken effect.
Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.
The File Manipulation Page
The File Manipulation page allows you to allow clients to upload files, delete files, create directories, remove directories, list the contents of a directory, and rename files on your server.For more information, see Enabling Remote File Manipulation.
The following elements are displayed:
Editing. Specifies a resource to which you want to enable remote file manipulation. If you choose a directory, the remote file manipulation applies only when the server receives a URL for that directory or any file in that directory.
Browse. Allows you to browse your primary document directory.
Wildcard. Specifies a wildcard pattern. For information on using wildcard patterns, see Wildcards Used in the Resource Picker.
Activate file manipulation commands. Determines whether remote file manipulation is enabled.
OK. Saves your entries. You must click Apply on the top right side of the page for your changes to take effect. If you do not click Apply after you update information, your changes are retained so that you can view and edit it, even though the changes have not taken effect.
Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.
The Document Preferences Page
The Document Preferences page allows you to specify the file name of your server's index, the type of indexing it will use, the server home page, the default MIME type, and whether or not your server will parse accept language headers.For more information, see Configuring Document Preferences.
The following elements are displayed:
Index Filenames. Specifies the file your server will look for and display if a user does not specify a document name in a URL. The server assumes that this file is the index file. The default files are index.html and home.html. If you enter more than one file name in this field, the server looks for the files in the order they are listed in the field until it finds one. For example, if your index file names are index.htmland home.html, the server first searches for index.html, and if the server does not find the file, it then searches for home.html. You can specify any file as an index file for a directory by naming it one of these default names, which means you can also use a CGI program as an index if CGI is activated.
Directory Indexing. Determines what type of directory index to generate if the server cannot find one of the index file names specified in the Index Filenames field. The generated index has one of the following formats:
Fancy. Fancy directory indexing includes a graphic that represents the type of file, the date the file was last modified, and the file size.
Home Page. Designates whether users will see a specified home page or an index file when they access your server. If you select Home Page, you must enter the URL of the home page in the field to the right of the radio button.Simple. Simple directory indexing displays directory entries as plain text hyperlinks and takes less time to generate than fancy indexing.
None. This setting specifies that no dynamic directory listing be generated if the server looks for index files and cannot find any. If the server does not find any index files, it will not display a directory listing and will return an error message.
If your server is outside the firewall, turn off directory indexing to ensure that your directory structure and file names are not accessible.
Index File. By default the server finds the index file specified in the Index Filename field and uses that for the home page.
Default MIME Type. Specifies the default MIME type the server returns if a client accesses a file with an extension that has not been set up as a MIME type on your server.
The default MIME type is usually text/plain, but you should set it to the type of file most commonly stored on your server. Some common MIME types include the following:
Parse Accept Language Header. Determines whether the server should parse accept language headers. Accept language headers are headers sent by clients using HTTP 1.1. These headers contain information describing the languages the clients accept.
For example, if you store documents in Japanese and English, you could choose to parse the accept language header. When clients that have Japanese as the accept language header contact the server, they receive the Japanese version of the page. When clients that have English as the accept language header contact the server, they receive the English version.
If you do not support multiple languages, you should not parse the accept language header.
OK. Saves your entries. You must click Apply on the top right side of the page for your changes to take effect. If you do not click Apply after you update information, your changes are retained so that you can view and edit it, even though the changes have not taken effect.
Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.
The URL Forwarding Page
The URL Forwarding page allows you to redirect document requests to another server. Forwarding URLs or redirection is a method for the server to tell a user that a URL has changed (for example, because you have moved files to another directory or server). You can also use redirection to seamlessly send a person who requests a document on one server to a document on another server.The following elements are displayed:
Add Another Forward
URL prefix. Specifies the URL prefix you want to redirect. For example, if the URL you want to map is http://www.iplanet.com/info/movies, you'd type /info/movies in this field. This setting forwards requests to a URL prefix, keeping the absolute path, and substituting one prefix for another. For example, if you forward
http://www.iplanet.com/info/movies to a prefix mozilla.com, the URL http://www.iplanet.com/info/movies redirects to
http://mozilla.com/info/movies.Sometimes you may want to redirect requests for all the documents in one sub-directory to a specific URL. For example, if you had to remove a directory because it was causing too much traffic, or because the documents were no longer to be served for any reason, you could direct a request for any one the documents to a page explaining why the documents were no longer available. For example, a prefix on /info/movies could be redirected to http://www.iplanet.com/explain.html.
Forward requests to. Specifies the destination URL.
URL prefix.
OK. Saves your entries. You must click Apply on the top right side of the page for your changes to take effect. If you do not click Apply after you update information, your changes are retained so that you can view and edit it, even though the changes have not taken effect.Fixed URL. Specifies that the text in this field is a fixed URL. If the directory structure on the new server is not the same as the directory structure on the mapped URL, you could forward the URL to a fixed URL. For example, you could forward http://www.iplanet.com/info/movies to:
- http://mozilla.com/new-files/info/movies.
Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.
Current Forwarding
Displays all URL forwardings currently defined on your server. To modify a URL forwarding, click Edit in the URL row. To delete a URL forwarding, click Remove in the URL row.
The Hardware Virtual Servers Page
The Hardware Virtual Servers page allows you to set your server to respond to multiple IP addresses without installing multiple servers. With hardware virtual servers you map multiple IP address to multiple document roots; for example, if you have two IP addresses, you could map the first IP address to one document root and the second IP address to a second document root. The iPlanet Web Server can respond to up to 5 IP addresses.Hardware virtual servers share the same server configuration information. For example, if you turn on encryption for one hardware virtual server, any other hardware virtual servers you create would also have encryption turned on.
For more information, see the following sections:
Setting Up Hardware Virtual Servers
The following elements are displayed:IP Address. Specifies your server's IP address that you want to map to a specific document root.
Document Root. Specifies the document root to which the IP address is to be mapped.
OK. Saves your entries. You must click Apply on the top right side of the page for your changes to take effect. If you do not click Apply after you update information, your changes are retained so that you can view and edit it, even though the changes have not taken effect.
Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.
Current Virtual Servers. Displays all virtual servers currently defined on your server (limited to 5). To modify a virtual server, click Edit in the virtual server row. To delete a virtual servers, click Remove in the virtual server row.
The Software Virtual Servers Page
The Software Virtual Servers page allows you to set up your server to host several web sites without needing to have more than one IP address on it. For example, you can set up your system so that both www.mozilla.com and www.iplanet.com resolve to 192.3.4.5, then set up software virtual servers to handle both server names (for example, http://www.mozilla.com/ and http://www.iplanet.com).The server can respond to requests differently depending upon the URL, even though the server only has one IP address. For example, one server can serve different pages for http://www.mozilla.com/ and http://www.iplanet.com.
The following elements are displayed:
Edit the default home page. Click this link to edit the document preferences for the default home page.
URL host. Specifies the name of the URL host whose custom home page you want to set up.
Home page. Specifies the path to the home page you want to use for this virtual server. If you type an absolute path, the server uses that specific document. If you type a partial path, the server interprets it as relative to your primary document directory.
OK. Saves your entries. You must click Apply on the top right side of the page for your changes to take effect. If you do not click Apply after you update information, your changes are retained so that you can view and edit it, even though the changes have not taken effect.
Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.
Current mappings. Displays all URL mappings currently defined on your server. To modify a URL mapping, click Edit in the URL mapping row. To delete a URL mapping, click Remove in the URL mapping row.
The International Characters Page
The International Characters page allows you to assign a character set to the documents on your server. The character set of a document is determined in part by the language in which it is written. You can override a client's default character set setting for a document, a set of documents, or a directory by selecting a resource and entering a character set for that resource.For more information, see To use the Server Manager for the hardware virtual servers that are uses with ISPs, see the section Setting Up Hardware Virtual Servers for ISPs.Changing the Character Set.
The following elements are displayed:
Editing. Specifies a resource to which you want to assign a character set. If you choose a directory, the character set applies only when the server receives a URL for that directory or any file in that directory.
Browse. Allows you to browse your primary document directory.
Wildcard. Specifies a wildcard pattern. For information on using wildcard patterns, see Wildcards Used in the Resource Picker.
Character set. Specifies the name of the character set to be used for the specified resource.
OK. Saves your entries. You must click Apply on the top right side of the page for your changes to take effect. If you do not click Apply after you update information, your changes are retained so that you can view and edit it, even though the changes have not taken effect.
Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.
The Document Footer Page
The Document Footer page allows you to specify a document footer, which can include the last-modified time, for all the documents in a certain section of the server without using server-parsed HTML. This footer works for all files except output of CGI scripts or parsed HTML (.shtml) files. If you need your document footer to appear on CGI-script output or parsed HTML files, enter your footer text into a separate file and add a line of code or another server-side include to append that file to the page's output.The following elements are displayed:
Editing. Specifies a resource to which you want to apply the document footer. If you choose a directory, the document footer applies only when the server receives a URL for that directory or any file in that directory.
Browse. Allows you to browse your primary document directory.
Wildcard. Specifies a wildcard pattern. For information on using wildcard patterns, see Wildcards Used in the Resource Picker.
For files of type. Specifies the type of files to include in the footer. The default is text/html.
Date Format. Specifies the date format.
Custom Date Format. Specifies a custom date format specified in the field to the right of the radio button.
Footer Text. Specifies the text that will appear in the footer. The maximum number of characters for a document footer is 765. If you want to include the date the document was last modified, type the string :LASTMOD:. Any entities (for example, ©) are contracted after you save your changes.
Note When you change the document footer for an HTML page, the last-modified date does not change.
OK. Saves your entries. You must click Apply on the top right side of the page for your changes to take effect. If you do not click Apply after you update information, your changes are retained so that you can view and edit it, even though the changes have not taken effect.
Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.
The Parse HTML Page
HTML is normally sent to the client exactly as it exists on disk without any server intervention. However, the server can search HTML files for special commands (that is, it can parse the HTML) before sending documents. If you want the server to parse these files and insert request-specific information or files into documents, you must first enable HTML parsing.The Parse HTML page sets the server to search HTML files for special commands (that is, it can parse the HTML).
The following elements are displayed:
Editing. Specifies a resource to which the server will parse HTML. If you choose a directory, the server will parse HTML only when the server receives a URL for that directory or any file in that directory.
Browse. Allows you to browse your primary document directory.
Wildcard. Specifies a wildcard pattern. For information on using wildcard patterns, see Wildcards Used in the Resource Picker.
Activate server-parsed HTML. Specifies whether server-parsed HTML is activated. The choices are:
No. The server does not parse HTML.
Parse which files. Specifies which files the server will parse. The choices are:Yes, with exec tag. The server parses HTML and allows HTML files to execute arbitrary programs on the server.
Yes, without exec tag. The server parses HTML, but does not allow HTML files to execute arbitrary programs on the server. You might not want to allow the exec tag for security or performance reasons.
Files with the extension .shtml. The server parses only files with the extension .shtml. In this case, all files you want to parse must have the .shtml extension. This is the most common (and default) choice.
OK. Saves your entries. You must click Apply on the top right side of the page for your changes to take effect. If you do not click Apply after you update information, your changes are retained so that you can view and edit it, even though the changes have not taken effect.All HTML files. The server parses all its HTML files. Choosing this option can slow your server's performance.
Unix/Linux. Parse files whose Unix/Linux permissions specify that the execute bit is on. Using the execute permissions can be unreliable because some files that are not executable have the bit set.
Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.
The Cache Control Directives Page
Cache-control directives are a way for iPlanet Web Server to control what information is cached by a proxy server. Using cache-control directives, you override the default caching of the proxy to protect sensitive information from being cached, and perhaps retrieved later. For these directives to work, the proxy server must comply with HTTP 1.1.The Cache Control Directives page allows you to control which information on your server can be cached by a proxy server.
For more information HTTP 1.1, see the Hypertext Transfer Protocol--HTTP/1.1 specification (RFC 2068) at:
The following elements are displayed:
- http://www.ietf.org/html.charters/http-charter.html
Editing. Specifies a resource to which you want to set cache-control directives. If you choose a directory, the server will set cache-control directives only when the server receives a URL for that directory or any file in that directory.
Browse. Allows you to browse your primary document directory.
Wildcard. Specifies a wildcard pattern. For information on using wildcard patterns, see Wildcards Used in the Resource Picker.
Cache Control Response Directives. Specifies what type of information is cachable. The choices are as follows:
Public. The response is cachable by any cache. This is the default.
OK. Saves your entries. You must click Apply on the top right side of the page for your changes to take effect. If you do not click Apply after you update information, your changes are retained so that you can view and edit it, even though the changes have not taken effect.Private. The response is only cachable by a private (non-shared) cache.
No Cache. The response must not be cached anywhere.
No Store. The cache must not store the request or response anywhere in nonvolatile storage.
Must Revalidate. The cache entry must be revalidated from the originating server.
Maximum Age (sec). The client does not accept a response that has an age greater than this age.
Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.
Previous Contents Index Next
Copyright © 2000 Sun Microsystems, Inc. Some preexisting portions Copyright © 2000 Netscape Communications Corp. All rights reserved.
Last Updated July 13, 2000