MORE INFORMATION
The SERK lists the settings for NoAbsoluteFileResults and
NoServerFileResults with a default value of 1. This is correct; however,
setting the value to "1" does NOT restrict the form handler to saving to
the results to the Web content area only.
To make the restriction, the NoServerFileResults setting must be equal to
"0." The corrected version and explanation of these configuration settings
is listed below:
NoAbsoluteFileResults
Initial value after installation:
A value of 1 for this parameter does not place restrictions on the default
(Save Results), Registration, and Discussion FrontPage form handling
components from writing results to a file path outside of the content
area. The parameter allows form results for form handling components to be
saved in any file path on the server that a FrontPage author has access
to.
A value of 0 for this parameter forces the default (Save Results),
Registration, and Discussion FrontPage form handling components write only
to a file within the customer's Web content area. It prevents these
FrontPage Components from writing to an absolute file path.
NoServerFileResults
Initial value after installation:
A value of "1" for this parameter allows the default (Save Results),
Registration, and Discussion FrontPage form handling components to write
to the _vti_log directory in the customer's document root.
Setting the NoServerFileResults parameter to "1" can be useful to allow
customers to save the output generated from the Save Results,
Registration, and Discussion FrontPage Components to the _vti_log
directory in the server's root web.
As a security measure, the Author.log file in the _vti_log directory
records all authoring actions on the Web when the Logging parameter is
set.
Setting the NoServerFileResults value to "0" for this parameter prevents
the default (Save Results), Registration, and Discussion FrontPage form
handling components from writing to the _vti_log directory in the
customer's document root. It also prevents an author from "covering his
tracks" by overwriting or modifying the Author.log file.
Application of settings on Windows Systems:
Both of the settings listed above are administered in the Frontpg.ini
configuration file for Windows platforms. By default, the Frontpg.ini file
is located in the Winnt folder in Windows NT and in the Windows folder in
Windows platforms.
To globally set the parameters above, make the changes under the
[FrontPage 3.0] section in the Frontpg.ini file. To make the setting only
apply to a particular virtual server, add the settings to the respective
Port section for the virtual server in the Frontpg.ini file.
Application of settings on Unix Systems:
On Unix, To globally set the parameters above, make the settings in the
Frontpage.cnf file, which is usually stored in the following path:
Usr/local/frontpage/version3.0/frontpage.cnf.
To make the settings only apply to a particular virtual server, add the
settings to the respective configuration file for that virtual server.
On multi-hosted systems, the configuration file is <hostname>:<port>.cnf
where <hostname> is the fully qualified domain name of the server.
On a single-host system, the file is we<nnn>.cnf where <nnn> is the Web
server's port number. In either case, the file is in Usr/local/frontpage
by default.