Previous Contents Index Next
Sun ONE Web Server 6.1 Administrator's Guide

> ## The Content Management Tab

> The Content Management tab allows you to manage content for all virtual servers in a class. The Content Management tab contains the following pages:

> - The Primary Document Directory Page
> - The Additional Document Directories Page
> - The User Document Directories Page
> - The Remote File Manipulation Page
> - The Document Preferences Page
> - The Enable/Disable WebDAV Page
> - The URL Forwarding Page
> - The Error Responses Page
> - The International Characters Page
> - The Document Footer Page
> - The .htaccess Configuration Page
> - The Symbolic Links Page
> - The Parse HTML Page
> - The Cache Control Directives Page
> - The Stronger Ciphers Page
> - The Serve Precompressed Content Page
> - The Compress Content on Demand Page

> ##

> The Primary Document Directory Page

> The Document Root Settings page is used to change the primary document directory (also called the document root). This is the central directory in which files that need to be made available to remote clients of the virtual server are stored. For more information, see Setting the Primary Document Directory.

> The following elements are displayed:

> ID. Lists all virtual servers in the class.

> Document Root. Specify the virtual server’s primary document directory (document root). The default is set at the class level. Use this field to override the default.

> Caution | Each virtual server usually has its own primary document directory. If virtual servers share a primary document directory, users could simultaneously modify the same document without knowing it.

> OK. Saves your entries.

> Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.

> Help. Displays online help.

> ##

> The Additional Document Directories Page

> The Additional Document Directories page allows you to add document directories to your class and map URLs to document directories. This page is used to create additional document directories for the documents. For more information, see Setting Additional Document Directories.

> The following elements are displayed:

> URL prefix. Specify 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. Specify the absolute path of the directory you want the URL prefix to map to, for example:

> C:/sunone/marketing/pubdocs/index.html

> Apply Style. Use the drop-down list to specify a configuration style to be applied to the additional directory’s configuration.

> OK. Saves your entries.

> Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.

> Help. Displays online help.

> Current Additional Directories. Lists all additional document directories on your server. To modify values for an additional document directory, click the Edit button in the directory row. To remove a directory’s mapping, click the Remove button.

> Edit. Click this button to edit an existing additional document directory. Make your changes on the page that displays, and then click OK. To toggle back to Add mode, click the word Add in the edit page title.

> Remove. Click this button to remove an additional document directory from the list. Note that the directory itself is not deleted, just the entry here.

> ##

> The User Document Directories Page

> The User Document Directories page (available on UNIX/Linux) is used to configure public information directories that allow all users on your server to create home pages and other documents without your intervention. These directories must be configured for the entire class, however; they cannot be customized for individual virtual servers.

> For more information, see Customizing User Public Information Directories (UNIX/Linux).

> Note | Until you configure these directories and click OK, the page displays the message “Public information directories are not currently active” at the top of the page. Once you have activated the directories, the message becomes “Public information directories are currently active. You can also deactivate them.” Click the word “deactivate” in the message to deactivate them.

> The following elements are displayed:

> User URL prefix. Specify the URL prefix for the user directory (~ is the default).

> Subdirectory. Specify the user’s subdirectory (public_html is the default).

> Password file. Specify whether you want the server to use the system’s password file or a user file you have created to look up users. The choices are:

> - System file. Select this to use the system’s password file.
> - This file. Select this to use a user file, and then specify the absolute path to the user file in the corresponding field.
> - Load entire database on startup. Select this to load the entire password file on startup.

> Apply Style. Use the drop-down list to specify a configuration style to be applied to the additional directory’s configuration.

> OK. Saves your entries.

> Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.

> Help. Displays online help.

> ##

> The Remote File Manipulation Page

> The File Manipulation page is used to allow clients to perform remote file manipulation tasks on your server. These tasks include uploading and deleting files, renaming files, creating and removing directories, and listing the contents of a directory. Remote file manipulation must be configured for the entire class, however; it cannot be customized for individual virtual servers.

> For more information, see Enabling Remote File Manipulation.

> The following elements are displayed:

> Editing. Use the drop-down list to specify a resource for which you want to enable remote file manipulation, and then click Go. If you choose a directory, the remote file manipulation applies only when the server receives a URL for that directory or for any file in that directory. You can also browse for a resource by clicking the Browse button.

> Go. Click this button after selecting a resource.

> Browse. Click this button to browse your primary document directory. Clicking Browse displays the Choose a Part of Your Server page (see The Choose a Part of Your Server Page). Clicking the Options button on this page displays browsing options. Clicking the Back button returns you to the previous page.

> Wildcard. Specify a wildcard pattern. For information about using wildcard patterns, see Wildcards Used in the Resource Picker.

> Activate file manipulation commands? Specify whether to activate or deactivate file manipulation commands for the specified resource.

> Caution | By activating these commands you allow remote browsers to change your server’s documents. You should restrict write access to the specified resource to prevent unauthorized tampering.

> OK. Saves your entries.

> Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.

> Help. Displays online help.

> ##

> ##

> The Document Preferences Page

> The Document Preferences page allows you to specify the file name of the index, the type of indexing it will use, the server home page, and the default MIME type. For more information, see Configuring Document Preferences.

> The following elements are displayed:

> Index Filenames. Specify 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, home.html, and index.jsp. If you enter more than one file name in this field, the server looks for the files in the order they are listed until a match is found. For example, if your index file names are index.html and home.html, the server first searches for index.html. If the file is not found, the server 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. Specify the type of directory index to generate if the server cannot find one of the index file names specified in the Index Filenames field. Choose one of the following formats for the generated index:

> - Fancy. This format includes a graphic that represents the type of file, the date the file was last modified, and the file size.
> - Simple. This format displays directory entries as plain text hyperlinks and takes less time to generate than fancy indexing.
> - None. This specifies that no dynamic directory listing will 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.

> Note | Enter only an absolute path.

> Caution | If your server is outside of the firewall, turn directory indexing off to ensure that your directory structure and file names are not accessible.

> File to use for error response when indexing is none. If you specified None for the directory indexing format and want to use a customized error response page, specify the path to the file.

> Home Page. Select this if you want users to see a specific home page when they access your server, and then enter the URL of the home page in the corresponding field.

> Index File. Select this if you want users to see an index file when they access your server. If you select Index File, by default, the server finds the index file specified in the Index Filenames field and uses that for the home page.

> Default MIME Type. Specify the default MIME type the server will return if a client accesses a file with an extension that has not been configured as a MIME type on your server.

> The default MIME type is usually text/plain, but this should be set to the type of file most commonly stored on your server. Common MIME types include the following:

> - text/html
> - text/plain
> - text/richtext
> - image/jpeg
> - image/gif
> - image/tiff
> - application/postscript
> - application/x-gzip
> - application/x-tar
> - audio/basic

> OK. Saves your entries.

> Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.

> Help. Displays online help.

> ##

> The Enable/Disable WebDAV Page

> The Enable/Disable WebDAV page allows you to enable or disable WebDAV at the level of the virtual server class. You can enable WebDAV at the server instance level, at the virtual server class level, or at the individual virtual server level.

> For more information about configuring WebDAV on your server, see Using WebDAV.

> The following elements are displayed:

> Virtual Server Class. Lists the virtual server classes.

> Enable/Disable WebDAV. Select or clear the “Enable DAV for class class” box to enable or disable WebDAV for the virtual server class.

> OK. Saves your entries.

> Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.

> Help. Displays online help.

> ##

> The URL Forwarding Page

> The URL Forwards page allows you to redirect document requests to another server. Forwarding URLs, or redirection, is a method used to tell users that a URL has changed (such as when files are moved to another directory or server). You can also use redirection to seamlessly send users requesting a document on one server to a document on another server. This setting affects all virtual servers in the class.

> The following elements are displayed:

> ### Add Another Forward

> URL prefix. Specify the URL prefix you want to redirect. For example, if the URL you want to map is http://www.sunone.com/info/movies, you’d enter /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.sunone.com/info/movies to a prefix mozilla.com, the URL http://www.sunone.com/info/movies redirects to http://mozilla.com/info/movies.

> You may want to redirect requests for all documents in one subdirectory to a specific URL. If you need to remove a directory because it is causing too much traffic or because the documents should no longer be served, you could direct a request for any one of the documents to a page explaining why the documents are no longer available.

> For example, a prefix on /info/movies could be redirected to http://www.sunone.com/explain.html.

> Forward requests to. Specify the destination URL. The choices are:

> - URL prefix. Select this to specify a URL prefix to which to forward, and enter the prefix in the corresponding field.
> - Fixed URL. Select this to specify that the text in this field is a fixed URL, and enter the text in the corresponding field. 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.sunone.com/info/movies to http://mozilla.com/new-files/info/movies.

> OK. Saves your entries.

> Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.

> Help. Displays online help.

> ### Current Forwarding

> Displays all URL forwardings currently defined on your server. To modify a URL forwarding, click the Edit button in the URL row. To delete a URL forwarding, click the Remove button.

> Edit. Click this button to edit a URL forwarding. Make your changes on the page that displays, and then click OK. To toggle back to Add mode, click the word Add towards the top of the page.

> Remove. Click this button to remove a URL forwarding.

> ##

> The Error Responses Page

> The Custom Error Responses page allows you to specify a file to send or a CGI program to run for each HTTP code. A custom error response can be used to provide detailed messages to clients when they encounter errors from your server. This setting affects all virtual servers in the class.

> For more information, see Customizing Error Responses.

> The following elements are displayed:

> Editing. Use the drop-down list to specify a resource for which you want to customize error responses, and then click Go. If you choose a directory, the customized error responses apply only when the server receives a URL for that directory or for any file in that directory. You can also browse for a resource by clicking the Browse button.

> Go. Click this button after selecting a resource.

> Browse. Click this button to browse your file system. Clicking Browse displays the Choose a Part of Your Server page (see The Choose a Part of Your Server Page). Clicking the Options button on this page displays browsing options. Clicking the Back button returns you to the previous page.

> Wildcard. Specify a wildcard pattern to edit. For information about using wildcard patterns, see Wildcards Used in the Resource Picker.

> Error code. Displays the error codes for which error responses can be customized. For each error code you want to customize, specify the absolute path to the file or CGI script that contains the error response.

> - Unauthorized. Specifies the file to display when a user requests a resource that requires credentials (user name and password), and the credentials provided are wrong or incomplete.
> - Forbidden. Specifies the file to display when the server does not have file system permissions to read a document, or if the server is not permitted to follow symbolic links. Also displays when users without access permissions try to access a document on the server that is protected by access control.
> - 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.

> File. Specify the absolute path to the file or CGI script that contains your customized error response.

> Note | To remove a customization for an error code, remove the file name from the File field.

> CGI. Select this box if the file is a CGI script.

> OK. Saves your entries.

> Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.

> Help. Displays online help.

> ##

> The International Characters Page

> The International Characters page allows you to assign a character set to the documents on your server. A document’s character set is determined in part by the language in which the document 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 specifying a character set for that resource. This setting affects all virtual servers in the class.

> For more information, see Changing the Character Set.

> The following elements are displayed:

> Editing. Use the drop-down list to specify a resource to which you want to assign a character set, and then click Go. If you choose a directory, the character set applies only when the server receives a URL for that directory or for any file in that directory. You can also browse for a resource by clicking the Browse button.

> Go. Click this button after selecting a resource.

> Browse. Click this button to browse your primary document directory. Clicking Browse displays the Choose a Part of Your Server page (see The Choose a Part of Your Server Page). Clicking the Options button on this page displays browsing options. Clicking the Back button returns you to the previous page.

> Wildcard. Specify a wildcard pattern. For information about using wildcard patterns, see Wildcards Used in the Resource Picker.

> Character set. Specify the name of the character set to be used for the selected resource.

> OK. Saves your entries.

> Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.

> Help. Displays online help.

> ##

> The Document Footer Page

> The Document Footer page allows you to specify a document footer, which can include the last-modified time for all 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 want a 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. This setting affects all virtual servers in the class.

> The following elements are displayed:

> Editing. Use the drop-down list to specify a resource to which you want to apply the document footer, and then click Go. If you choose a directory, the document footer applies only when the server receives a URL for that directory or for any file in that directory. You can also browse for a resource by clicking the Browse button.

> Go. Click this button after selecting a resource.

> Browse. Click this button to browse your primary document directory. Clicking Browse displays the Choose a Part of Your Server page (see The Choose a Part of Your Server Page). Clicking the Options button on this page displays browsing options. Clicking the Back button returns you to the previous page.

> Wildcard. Specify a wildcard pattern. For information about using wildcard patterns, see Wildcards Used in the Resource Picker.

> For files of type. Specify the type of files to include in the footer. The default is text/html.

> Date Format. To select a date format from a drop-down list, select this option and then choose a format from the list.

> Custom Date Format. To specify a custom date format, select this option and then enter a custom format (for example, %B %d, %y).

> Footer text. Specify 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, &copy;) 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.

> Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.

> Help. Displays online help.

> ##

> The .htaccess Configuration Page

> The .htaccess Configuration page allows you to configure the use of .htaccess files for access control. For more information about the use of .htaccess dynamic configuration files, see Using .htaccess Files.

> The following elements are displayed:

> Editing. Use the drop-down list to select the resource to which to apply .htaccess configuration, and then click Go. You can also browse for a resource by clicking the Browse button.

> Go. Click this button after selecting a resource.

> Browse. Click this button to browse your primary document directory. Clicking Browse displays the Choose a Part of Your Server page (see The Choose a Part of Your Server Page). Clicking the Options button on this page displays browsing options. Clicking the Back button returns you to the previous page.

> Wildcard. Specify a wildcard pattern. For information about using wildcard patterns, see Wildcards Used in the Resource Picker.

> Activate .htaccess? Select Yes to activate .htaccess configuration for the specified resource. This is set to No by default.

> File Name. Specify the file name where you want the .htaccess configuration to be added.

> OK. Saves your entries.

> Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.

> Help. Displays online help.

> ##

> The Symbolic Links Page

> The Limit Symbolic Links page (available on UNIX/Linux) allows you to limit the use of file system links in your server. File system links are references to files stored in other directories or file systems. The reference makes the remote file as accessible as if it were in the current directory. This setting affects all virtual servers in the class.

> For more information, see Restricting Symbolic Links (UNIX/Linux).

> The following elements are displayed:

> Editing. Use the drop-down list to specify a resource for which to configure symbolic links, and then click Go. If you choose a directory, the symbolic links will apply only when the server receives a URL for that directory or for any file in that directory. You can also browse for a resource by clicking the Browse button.

> Go. Click this button after selecting a resource.

> Browse. Click this button to browse your file system. Clicking Browse displays the Choose a Part of Your Server page (see The Choose a Part of Your Server Page). Clicking the Options button on this page displays browsing options. Clicking the Back button returns you to the previous page.

> Wildcard. Specify a wildcard pattern to edit. For information about using wildcard patterns, see Wildcards Used in the Resource Picker.

> Allow soft file system links. Specify whether to allow soft file system links. A symbolic link consists of two files, an original file that contains the data, and another file that points to the original file. Symbolic links are more flexible than hard links. Symbolic links can be used across different file systems and can be linked to directories. The choices are:

> - Always. Always allow soft file system links.
> - Never. Never allow soft file system links.
> - Only When Owners Match. Allow soft file system links only when the owners match (when the owner is the same for both files).

> Allow hard file system links. Specify whether to allow hard file system links. A hard link is really two file names that point to the same set of data blocks; the original file and the link are identical. For this reason, hard links cannot be on different file systems.

> From Directory. Specify the path where the server should start looking for file system links. If you enter an absolute path, the server treats that path as a prefix. When it recognizes that prefix in a request, the server checks any directories following the prefix for file system links. If you enter a partial path, the server looks for that partial path as a substring of the incoming request. If you enter nolinks, the server looks for a directory called nolinks in the incoming request. If it finds that directory, it checks all following directories for file system links.

> OK. Saves your entries.

> Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.

> Help. Displays online help.

> ##

> The Parse HTML Page

> The Parse HTML page allows you to configure the server to search HTML files for special commands (parse the HTML). For more information, see Setting up Server-Parsed HTML.

> HTML is normally sent to the client exactly as it exists on disk without any server intervention. But the server can search HTML files for special commands 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. This setting affects all virtual servers in the class.

> The following elements are displayed:

> Editing. Use the drop-down list to specify a resource for which the server will parse HTML, and then click Go. If you choose a directory, the server will parse HTML only when the server receives a URL for that directory or for any file in that directory. You can also browse for a resource by clicking the Browse button.

> Go. Click this button after selecting a resource.

> Browse. Click this button to browse your primary document directory. Clicking Browse displays the Choose a Part of Your Server page (see The Choose a Part of Your Server Page). Clicking the Options button on this page displays browsing options. Clicking the Back button returns you to the previous page.

> Wildcard. Specify a wildcard pattern. For information about using wildcard patterns, see Wildcards Used in the Resource Picker.

> Activate server-parsed HTML? Specify whether you want server-parsed HTML to be activated. The choices are:

> - No. The server does not parse HTML.
> - 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 may not want to allow the exec tag for security or performance reasons.

> Parse which files? Specify which files the server will parse. The choices are:

> - 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.
> - Files with the execute bit and the extension .shtml. (UNIX/Linux only) The server parses files whose UNIX/Linux permissions specify that the execute bit is on. Using the execute permissions can be unreliable because in some cases the bit is set on files that are not executable.
> - All HTML files. The server parses all HTML files. Choosing this option can slow server performance.

> OK. Saves your entries.

> Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.

> Help. Displays online help.

> ##

> The Cache Control Directives Page

> The Cache Control Directives page allows you to control the information on your server that can be cached by a proxy server. This setting affects all virtual servers in the class. For more information, see Setting Cache Control Directives.

> Cache control directives are one way Sun ONE Web Server controls the information that is cached by a proxy server. Cache control directives allow you to override the default caching of the proxy to protect sensitive information from being cached and possibly retrieved at a later time. For these directives to work, the proxy server must comply with HTTP/1.1.

> For more information about HTTP/1.1, see the Hypertext Transfer Protocol--HTTP/1.1 specification (RFC 2068) at:

> http://www.ietf.org/rfc/rfc2068.txt?number=2068

> The following elements are displayed:

> Editing. Use the drop-down list to specify the resource to which you want to set cache control directives, and then click Go. If you choose a directory, the server will set cache control directives only when the server receives a URL for that directory or for any file in that directory. You can also browse for a resource by clicking the Browse button.

> Go. Click this button after selecting a resource.

> Browse. Click this button to browse your primary document directory. Clicking Browse displays the Choose a Part of Your Server page (see The Choose a Part of Your Server Page). Clicking the Options button on this page displays browsing options. Clicking the Back button returns you to the previous page.

> Wildcard. Specify a wildcard pattern. For information about using wildcard patterns, see Wildcards Used in the Resource Picker.

> Cache Control Response Directives. Specify the type of information that is cacheable. The choices are:

> - Public. The response is cacheable by any cache. This is the default.
> - Private. The response is cacheable only by a private (nonshared) 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 with an age greater than the age specified in the corresponding field.

> OK. Saves your entries.

> Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.

> Help. Displays online help.

> ##

> The Stronger Ciphers Page

> The Enforce Strong Security Requirements page allows you to set stronger ciphers. For more information, see Setting Stronger Ciphers.

> The following elements are displayed:

> Editing. Use the drop-down list to select the resource to which to apply stronger ciphers, and then click Go. If you choose a directory, the server will apply stronger ciphers only when the server receives a URL for that directory or for any file in that directory. You can also browse for a resource by clicking the Browse button.

> Go. Click this button after selecting a resource.

> Browse. Click this button to browse your primary document directory. Clicking Browse displays the Choose a Part of Your Server page (see The Choose a Part of Your Server Page). Clicking the Options button on this page displays browsing options. Clicking the Back button returns you to the previous page.

> Wildcard. Specify a wildcard pattern. For information about using wildcard patterns, see Wildcards Used in the Resource Picker.

> Key size restriction. Select one of the following secret key sizes to be required for access:

> - 168 bit or larger
> - 128 bit or larger
> - 56 bit or larger
> - No restrictions

> Reject access with file. Enter the file location of the message used to reject access.

> OK. Saves your entries.

> Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.

> Help. Displays online help.

> ##

> The Serve Precompressed Content Page

> The Precompressed Content Configuration page allows you to administer precompressed content. A compressed version of a file must have the same file name as the noncompressed version, but with a .gz suffix.

> The following elements are displayed:

> Editing. Use the drop-down list to select the resource from which precompressed content will be served, and then click Go. If you choose a directory, the server will serve precompressed content only when the server receives a URL for that directory or for any file in that directory. You can also browse for a resource by clicking the Browse button.

> Go. Click this button after selecting a resource.

> Browse. Click this button to browse your primary document directory. Clicking Browse displays the Choose a Part of Your Server page (see The Choose a Part of Your Server Page). Clicking the Options button on this page displays browsing options. Clicking the Back button returns you to the previous page.

> Wildcard. Specify a wildcard pattern. For information about using wildcard patterns, see Wildcards Used in the Resource Picker.

> Activate Serving Precompressed Content? Specify whether the server should serve precompressed content for the selected resource. The choices are:

> - No. Precompressed content is not served.
> - Yes. Precompressed content is served.

> Check Age? Specify whether to check if the compressed version is older than the noncompressed version. The choices are:

> - No. The compressed version, even if it is older than the noncompressed version, will always be selected.
> - Yes. The compressed version, if it is older than the noncompressed version, will not be selected. The value is set to Yes by default.

> Insert Vary Header? Specify whether to insert a Vary: Accept-encoding header. The choices are:

> - No. A Vary: Accept-encoding header is never inserted.
> - Yes. A Vary: Accept-encoding header is always inserted when a compressed version of a file is selected. The value is set to Yes by default.

> OK. Saves your entries.

> Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.

> Help. Displays online help.

> ##

> The Compress Content on Demand Page

> The Compress Content on Demand Configuration page allows you to dynamically compress the requested resource. A compressed version of a file must have the same file name as the noncompressed version, but with a .gz suffix.

> The following elements are displayed:

> Editing. Use the drop-down list to select the resource from which compressed content will be served dynamically on demand, and then click Go. If you choose a directory, the server will serve compressed content only when the server receives a URL for that directory or for any file in that directory. You can also browse for a resource by clicking the Browse button.

> Go. Click this button after selecting a resource.

> Browse. Click this button to browse your primary document directory. Clicking Browse displays the Choose a Part of Your Server page (see The Choose a Part of Your Server Page). Clicking the Options button on this page displays browsing options. Clicking the Back button returns you to the previous page.

> Wildcard. Specify a wildcard pattern. For information about using wildcard patterns, see Wildcards Used in the Resource Picker.

> Activate Compress Content on Demand? Specify whether the server should serve precompressed content for the selected resource. The choices are:

> - No. Precompressed content is not served.
> - Yes. Precompressed content is served.

> Insert Vary Header? Specify whether to insert a Vary: Accept-encoding header. The choices are:

> - No. A Vary: Accept-encoding header is never inserted.
> - Yes. A Vary: Accept-encoding header is always inserted when a compressed version of a file is selected. The value is set to Yes by default.

> Fragment Size. Specify the memory fragment size in bytes to be used by the compression library (zlib) to control the rate of compression (the amount to compress at one time). The default value is 8096.

> Compression Level. Use the drop-down list to specify the level of compression. Choose NONE or a value between 1 and 9. The value 1 yields the best speed; the value 9 the best compression. A middle value provides a compromise between speed and compression.

> OK. Saves your entries.

> Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.

> Help. Displays online help.

> Previous Contents Index Next

> Copyright 2004 Sun Microsystems, Inc. All rights reserved.