User's Guide
Configuring NetCloak
Contents
|
Version 3.1 User's Guide |
Configuring NetCloak |
Previous |
Next Contents |
NetCloak has a number of options and parameters that you can configure that control how it serves, creates and logs files on your server. NetCloak provides a convenient web-based interface for setting these as well as editing counters, variables and all of the other administrative information. The CGI application also has a traditional GUI which provides the same functions.
The web-based administration pages are the recommended method of configuring the NetCloak plug-in. You may also use the web admin pages with the NetCloak CGI, but you must first enable access using the "Enable web administration" checkbox in the Security tab of the Configuration window (see below).
To access the browser-based web admin pages, access the following URL in your browser (replacing "your.domain.com" with your server's actual domain name or IP address):
http://your.domain.com/pi_admin.nclk
Unless you have already entered a valid username and password for the pi_admin realm on your web server, your browser will display a dialog box requesting a username and password. Most Macintosh web servers, including WebStar and WebTen, automatically require a username and password to access any URL containing "pi_admin", so that only authorized users may change plug-in configuration settings. If you have not previously logged in as an admin user, and you aren't presented with a login dialog when accessing this URL, then your server does not automatically require a password for pi_admin URLs. You should immediately create one before continuing. Consult your web server's documentation on how to create a realm. Failing to protect pi_admin URLs represents a severe security risk for your web server.
Once you have logged in as an admin user, you are shown the main NetCloak status page. Links at the top of the page allow you to navigate to other admin pages.
Note for AppleShare IP users: AppleShare IP 5.0 does not handle special URLs which do not represent actual files in the web server root folder, such as the NetCloak admin URL. If you access the above URL, you will be presented with a "file not found" error message. To work around this problem, you can create an empty file named "pi_admin.nclk" in your Web root folder. The file must be completely empty (zero bytes in length). With this file present, AppleShare IP will ask NetCloak to process it. NetCloak will then ignore the file and serve its internally-generated admin web page instead.
Figure 11: The Files tab of the NetCloak Configuration window.
When using the CGI version of NetCloak, you may alternatively use the commands in the "Configuration" menu in the NetCloak CGI application. The "Configure…" command displays the NetCloak Configuration window. While it is possible to use the CGI's Configuration window to administer the plug-in, this is not recommended.
The first tab of the Configuration window allows you to set the root folder and special file names needed by NetCloak.
There are three special files NetCloak requires to handle certain HTML requests.
Default Page: The name of the page NetCloak will look for when the user specifies only a directory (including the root domain). For example, if the default page is set to "HomePage.html", then NetCloak will look for that filename by default when only a directory is specified by an incoming URL request.
Figure 12: The Files page of the NetCloak Web admin interface.
Note that this field should not begin with a colon (':') character, since this field specifies a filename, not the path to an actual file. The filename in this field is appended to the incoming URL.
Error Page: When NetCloak is unable to find a file thatmatches an incoming URL, the Error Page is returned. This field specifies an actual file to be returned; thus, it contains the path to the file, relative to the configured Root Folder. If the error file is in the Root Folder, then this field should begin with a colon (':') followed by the name of the file.
If the field does not begin with a colon, then NetCloak looks for the error file in the same folder as the requested file. Although this is an unusual setup, it can be used to provide a custom error page for every folder on your web site.
A CGI application can also be specified as the error file, in which case NetCloak will call the CGI to handle the bad request. If the error file is suffix-mapped to a "back-end" CGI or plug-in in the "NetCloak.bsm" file, NetCloak will also call the back-end CGI or plug-in to process the error file. In either case, any NetCloak commands in the text returned from the "error CGI" are processed before returning the response to the browser.
When serving multiple virtual domains from your web server, the named Error Page must exist in each virtual domain's root folder. Since NetCloak can resolve aliases, you may simply create an alias to an Error Page in each virtual domain's root folder.
No Access Page: The "No Access" page is returned when a user is denied access to a page because their IP address is denied or because they fail to enter a correct username and password for a password protected page. This field, too, represents the path to an actual file, so it should also begin with a colon, followed by the filename, if it represents a file in the web server Root Folder. As with the Error Page setting, this field may contain the path to a CGI, or the path to a file which is suffix-mapped to a back-end CGI or plug-in.
Ask Server – (CGI only) Most web servers also have their own settings for the three special file names. In particular, WebSTAR and WebTen provide access to these filenames via AppleScript, so NetCloak can retrieve the file names directly from either of these two web servers when you click this button. The button is only enabled if one of these two servers is up and running on the same machine along with NetCloak. If you are using another web server, this button will not work, and you will have to set the filenames manually.
Ask Server for File Names – (Plug-In only) Some web servers allow the administrator to configure separate default, error, and no-access files for multiple virtual domains. The NetCloak plug-in can get the names of the three files directly from the web server, on the fly, as each request is processed. This lets it use the correct file names for each request to a virtual domain. Check this checkbox in the NetCloak web admin "Files" page to configure NetCloak this way. If you want the NetCloak plug-in to always use the file names configured in NetCloak, uncheck this checkbox.
Choose the folder NetCloak should serve files from. To select the folder, click on the "Root Folder" button and choose the folder with the standard file dialog box that appears.
The selected Root Folder is used as the root folder for all NetCloak commands which accept a relative path, including macros, back-end CGIs and NetCloak aliases.
In most cases, the Root Folder will be the same folder as your web server's root folder. The ability to select the Root Folder has two important advantages. First, when using the NetCloak CGI, this allows you to put the CGI application anywhere you wish, for example, in a "cgi-bin" folder, while serving from the web server root. In addition, the NetCloak root folder is not required to be the same as the server root folder. For example, if you are concerned about security, you can put your NetCloak files into a separate folder hierarchy from the main server folder structure. This will ensure that files that are supposed to be cloaked are never inadvertently served by your server without NetCloak processing them. Since the cloaked files will be outside of your web server folder, the server will never be allowed to serve them.
Important Note: This assumes you are running a server that restricts access to a web server root folder and that you have not placed any Finder aliases in your server root folder that would permit access to the NetCloak -defined root folder. It also does not take into consideration other CGIs that might be able to serve files outside the web server root.
Ask Server For Root Folder -- If the server supplies a root folder as part of the CGI AppleEvent or WebSTAR API request, and this option is checked, NetCloak will disregard the configured Root Folder setting and serve from the folder specified by the web server. Many web servers support this parameter, and selecting this option is the best way to ensure seamless file services when using NetCloak in conjunction with your server. This is especially true of servers that support multiple root folders for different domains. In this case, the folder to serve from may be different for each request that is processed by NetCloak. When this option is checked, NetCloak will always serve the file from the appropriate folder, as intended.
Note that when this option is checked, NetCloak will use the root folder specified by the server for each request that it receives. NetCloak will still use the folder selected with the "Root Folder" button to locate NetCloak aliases and other files that are read during startup or outside of any HTTP connection request.
Figure 13: The Options page of the NetCloak web admin
NetCloak supports several features that allow you to improve how your server behaves in different situations and for different browsers. To select these preferences, use the HTTP/HTML tab of the configuration window.
Server Name -- The "Server Name" field is used by NetCloak to build the HTTP header returned to the client, and tells the client what server software is being used. The server name can be important for several reasons, and you should set this field carefully.
First, this field is used by many Web crawlers (also known as "robots") for studies that determine what software is being used by whom on the Internet. By correctly returning the name of your server, you are helping to promote the Mac OS platform and the server software you have chosen. This is not a trivial issue, and we strongly urge you to enter the correct name of your server software and the name "NetCloak". If you choose, you may list the names of other server applications, and they should be listed in order of importance, with the server itself always listed first.
It is not necessary to include the version numbers of the server, NetCloak, or any other server application. In fact, for security reasons, it is a good idea to leave the version number off. However, if you like, you may list the version numbers. If you choose to do this, the version number should follow the name of the application, with a slash ("/") between them, and no spaces. For example, you could set this field to:
WebSTAR/4.2.1 NetCloak/3.1
Complete information on the server field can be found in the HTTP/1.1 specification, RFC 2068, section 14.39.
Last Modified -- Another field of the HTTP header is the "Last-Modified" date of the file. This field presents special issues when using NetCloak, because NetCloak is constantly changing the contents of files. However, it is important to use this field so that proxy servers and Web browser will correctly cache cloaked pages, and so that search engines will properly update their indexes when you update the contents of a page.
To solve this problem, there are three options:
Exclude From Header : When you select this option, NetCloak will not include the Last-Modified field in the header at all. This is a legal option, and is provided for in the HTTP specification. By choosing this, you are essentially leaving caching decisions up to proxies and browsers that access the page. It is not recommended, though, because caching is much more effective when the last-modified date is present. In addition, search engines often will not properly index pages that have no last-modified date.
Send File's Modified Date : If your site does not make excessive use of NetCloak's dynamic commands, your best option is to return the actual date the last time the file was modified. This is the same thing your server would do if the file was being served without NetCloak. This option, along with "Pragma: No-Cache for dynamic pages" is the preferred setting. Your pages will be crawled and updated correctly by search engines, but proxy servers and Web browsers will not cache them.
Send Current Date/Time : For pages that are very dynamic, and that should always be loaded from the server, use the "Send Current Date/Time" option. This will always send the date and time that the page is being served as the files last modified date. This may seem like a trick, but it is the most reasonable setting, in many cases. NetCloak modifies files as they are being served, so reporting the current date and time is, in fact, accurate.
Note that this default setting can be overridden on a page by page basis using the SET_NETCLOAK configuration command within your pages. You might want to do this if most of your pages are relatively static, with only a couple of very dynamic pages used on your site. In this case, you could set the default to "Send File's Modified Date" but use the SET_NETCLOAK command to send the current date and time for the very dynamic pages.
"Pragma: No-cache" for dynamic pages – Caching proxy servers and most Web browsers sometimes will cache a page even when the Last-Modified setting is set to "Current Date/Time". Checking this checkbox causes NetCloak to include a "Pragma: No-cache" field in the HTTP response header when the page contains any NetCloak command that causes the page's content to change with every request. This includes all SHOW, HIDE and INSERT commands, and many others. When "Pragma: No-cache" is present in the response header, HTTP 1.0 and 1.1 compliant proxy servers and browsers will not cache the page, regardless of the Last-Modified date or any other HTTP header field.
When Serving -- NetCloak will convert Mac Roman extended characters to ISO-Latin-1 character encoding or HTML entities. For US-ASCII only Web sites, leave this option on "No Translation", but if you use extended characters, you can select an appropriate translation and edit your documents using the standard Mac OS character set. When these pages are served, the characters will be converted as specified so that they appear correctly in the user's browser, regardless of the platform or operating system they are using.
When Saving -- NetCloak will convert ISO-Latin -1 character encodings or HTML entities in submitted form data to Mac Roman extended characters in created or updated files according to the selected option:
None – Performs no character conversion.
ISO-Latin -1 to MacRoman -- Convert "extended" ASCII characters (with ASCII values greater than 128) from the ISO-8859-1 (ISO-Latin-1) character set to the MacRoman character set, so that the file is in a standard Macintosh text format. When such characters are viewed in a Macintosh text application, they will appear as the expected Mac extended characters (the apple symbol, the bullet symbol, etc.). When viewed in a web browser, however, unexpected "garbage characters" may appear—particularly if the browser is running on something other than the Mac OS.
Convert from HTML Entities -- When this option is selected, extended characters in the form data are converted into the HTML-defined "entity" codes (such as " "), so that they appear correctly in HTML documents viewed in any Web browser.
For all of these options, the only way to know for sure what will work best for you is to test your site with a variety of browsers. There is (unfortunately) a wide variety of ways in which browsers treat extended characters, as well as the caching of pages based on the last-modified date. Decide what browsers are important to support at your site, download them, and try the various options to determine the best selection.
NetCloak sometimes needs to create text files on your server. Most often, it is creating log files or files that contain configuration information such as the list of defined groups. Files will be most commonly created when processing forms with NetCloak Pro. When it needs to create a text file, you can specify what application opens the file when it is double-clicked.
Creator Signature – Enter into this field the four-character creator code of the application that you wish to use to edit text files. By default, NetCloak uses the signature 'R*ch', the creator signature of BBEdit. If you don't know the creator signature of your favorite text-editing application, use the "Same Creator As…" button.
Same Creator As… -- Clicking this button presents a standard file dialog box, which lets you select any text file. NetCloak will then enter the creator signature of the selected file into the "Creator Signature" field automatically.
Very often, a web server administrator wantsto include a common header or footer on every page on their web site. NetCloak makes this a snap with its MACRO and MODEMACRO commands. However, this requires you to insert the macro command into the top and bottom of every page by hand. If you have hundreds or thousands of existing pages, this becomes an daunting task. Also, you cannot add macro commands to pages whose content you do not control, including pages that are generated on-the-fly by back-end CGIs or plug-ins.
In those situations, you can use NetCloak AutoMacros. As the name suggests, AutoMacros are macros that are automatically added to Web pages processed by NetCloak. You may define a header AutoMacro and a footer AutoMacro.
Header – Enter into this field the name of a macro contained in the "NetCloak.macros" file, or the path to a macro file, using the exact same syntax as you would for the filepath parameter in a MACRO or MODEMACRO command. When this field is filled in, NetCloak inserts an equivalent MODEMACRO command into each cloaked page, just after the <BODY> tag that begins the page content. If no <BODY> tag is present in the page, NetCloak looks for a </HEAD> tag, and then a <HTML> tag. If none of these tags is present, NetCloak inserts the header AutoMacro at the top of the page.
Footer – Similarly, this field contains the name or filepath of a MODEMACRO to be inserted into each cloaked page, just before the </BODY> tag that ends the page content. If no </BODY> tag is present, it looks for a </HTML> tag. If neither tag is present, the footer AutoMacro is added to the bottom of the page.
If you do not wish to use AutoMacros, then leave these two fields empty.
Date – Use this popup menu to set the default date format used by INSERT_DATE and other NetCloak commands that insert dates. The first item in the menu displays your server's current Short Date format, and the second item displays your server's current Long Date format. The Short Date and Long Date formats are defined in the Mac OS Date & Time control panel on the server. See the Date and Time control panel's "Date Formats" setting to configure the short and long date formats. The default date format may be overridden within each NetCloak date command that has a format parameter.
Time – This popup menu displays the Short Time format and the Long Time format currently configured on your server. When the Short Time menu item is selected, all times inserted by NetCloak commands such as INSERT_TIME will be shown as hours and minutes, without seconds. When the Long Time format is selected, times will be displayed with seconds. The time formats displayed in the popup menu are configured in the Mac OS Date & Time control panel on the server. The default time format may be overridden within each NetCloak time command that has a format parameter.
Enable Dynamic Caching NetCloak supports a dynamic file cache that will automatically store your most frequently accessed files in RAM for faster retrieval and serving. The files NetCloak will store in RAM are selected based upon the amount of available RAM and the frequency with which files are accessed. To disable this feature, uncheck this box.
Flush Dynamic Cache – Use this button (CGI) or link (in the Web admin interface) to immediately force NetCloak to remove all cached files from its dynamic cache. This forces NetCloak to re-read all files from disk again, and frees up RAM in the application heap.
Figure 14: The HTML page of the NetCloak Web admin interface.
Reload Documents – Use this button (CGI) or link (in the Web admin interface) to tell NetCloak to re-read all files that are normally read and loaded into RAM at startup. This includes:
all files listed in NetCloak.config
NetCloak.groups
NetCloak.macros
NetCloak can maintain a log in addition to the one created by your web server. Information included in the basic log is date and time of the request, status, the user's IP address or domain, the file requested, and the size of the response. The NetCloak extended log adds the username, password, referrer, and browser type. This extra information is added at the end of each line, so it should not interfere with log analyzing programs that expect only basic information.
One advantage to using the NetCloak log is that it will log only your HTML pages. When a client requests a page with multiple images on it, your web server log will contain several entries, one for the HTML page and another for each of the images linked into the page. This redundancy is often unneeded, and causes your log files to quickly become very large. In addition, the web server incurs the overhead associated with logging each page served multiple times.
Figure 15: The Logs page of the NetCloak Web admin interface.
By shutting off your web server log, server performance will improve and your logs will be more manageable. The NetCloak log can then be used to show you who has visited your site and when. Of course, NetCloak will only log those file requests that it processes, so be aware that some site access will not be logged at all. This may not be appropriate for all Web sites, but for those whose logging requirements aren't as strict it is an excellent way to improve performance and simplify site management.
To set logging preferences, choose the "Logs" tab of the Configuration window.
You can choose whether to maintain a standard log, an extended log, or skip logging entirely. You can also choose to store the log information anywhere on your hard drive by clicking the "Log File" button and selecting a file to keep the log.
When strange problems occur, you can "Enable Debug Logging" in NetCloak. This causes NetCloak to create a file named "NetCloak Debug Log" located in the NetCloak Files folder, which contains very detailed debugging information about NetCloak processing. This information is mostly useful to engineers here at Maxum when debugging software problems, so you should ordinarily leave this option disabled unless instructed to enable it by Maxum tech support personnel.
NetCloak provides several security options designed to make your server as secure as you need it to be while giving you flexibility that is not possible with your web server alone. Much of NetCloak's security benefits are found in the commands themselves, but there are also several options you can select from on the "Security" tab of the Configuration window.
Don't serve files with creator code 'WWWΩ' – This option lets you specify that Mac OS files created by certain applications are not allowed to be served through NetCloak. The default setting is to prevent any file created by WebSTAR (with creator code 'WWWΩ') from being served, which protects the sensitive information contained in the WebSTAR Settings and WebSTAR.pass files created by WebSTAR. If you use some other web server software, you may want to change this setting to the creator code of that application. Utilities such as ResEdit or shareware such as Snitch or FileTyper allow you to view and/or modify the creator codes of files.
Enable web administration – (CGI only) By default, the NetCloak CGI does not allow access to the Web browser administration pages. To be able to edit configuration settings of the NetCloak CGI from any Web browser, check this checkbox. Web administration is always enabled in the NetCloak plug-in, since it is the only way to access the plug-in's configuration settings.
Figure 16: The Security page of the NetCloak Web admin interface.
Prohibit root-relative file paths in tags – This security setting is most useful to web server administrators who host Web pages for users who are allowed to modify their own pages. When this box is checked, file paths in all NetCloak commands are restricted to files in the same folder as the current page, or lower, using "file-relative" paths. In other words, only paths that do not begin with a colon or slash are allowed. This prevents any cloaked page from accessing information stored in any page outside the same folder. This setting is useful to few users and should ordinarily be left unchecked, which is the default setting.
Only serve files listed in "NetCloak.config" -- When this option is checked, NetCloak will not serve a requested file unless it is aliased by a line in the "NetCloak.config" file. This represents the ultimate level of security provided by NetCloak. In this mode of operation, users visiting your web site can only see aliased files, and the aliases used in your URLs can give the illusion of an entire folder hierarchy that doesn't even exist! By default, this option is not checked, allowing any files accessible by your web server software to be cloaked.
See the section "NetCloak Aliases and Caching" for information on NetCloak aliases.
Only process macros listed in "NetCloak.macros" -- Because MACRO commands may refer to files located anywhere in your web server root folder, malicious users may attempt to gain access to sensitive files on your server by uploading files or submitting data which contain such MACRO commands. To eliminate this possibility, you can check this option. When checked, you have complete control over which macros may be executed on your server -- only those macros entered into the "NetCloak.macros" file will be allowed to run.
If NetCloak is unable to insert a macro because this option is checked, it will insert an error message enclosed in an HTML comment in place of the MACRO command when the document is served.
Prohibit EXEC_CGI tags -- This option is fairly straightforward. When checked, NetCloak will not process EXEC_CGI commands. The EXEC_CGI command poses a security risk because malicious users may attempt to upload CGI files to your server and then call these CGIs by uploading HTML files containing EXEC_CGI commands. Or they may attempt to use your existing CGIs in a destructive manner. By default, this option is checked. To enable EXEC_CGI commands on your server, you must un-check this option.
If this option is checked, NetCloak will insert an error message enclosed in an HTML comment in place of the EXEC_CGI command when the document is served.
Convert angle brackets to html entitiesÑ This checkbox determines whether or not articles containing the less-than (<) and greater-than (>) brackets should be converted into their HTML encoded equivalents for use on the Web. HTML reserves a small number of ASCII characters for use as formatting instructions, including the (<) and (>) brackets, and if these characters are to be used in the body of an HTML document they must be first converted. Checking the ÒConvert angle bracketsÉÓ option will convert these brackets into their HTML character tag equivalents, Ò<Ó (for less-than, '<') and Ò>Ó (for greater-than, '>'). When checked, articles containing greater than and less than symbols will not produce unexpected formatting when they are submitted and converted to HTML documents on your server.
When not checked, NetCloak Pro will simply leave the brackets in the user-entered text when it is inserted. This allows users to enter HTML tags and markup their articles.
The security advantage of selecting this option is that you will be able to prevent authors from embedding HTML tags in their articles, including formatting commands, images, and links to other pages. The downside, of course, is that if this option is selected, users won't have the option of entering HTML tags on their own to enhance the formatting of their pages.
Restrict access to root folderÑ When this checkbox is checked, all FDML activity is restricted to the configured Root Folder. No file outside this folder can be opened, read from, written to, or created in any way whatsoever. This rule is applied to all FDML primary and supplemental directives, so that, for instance, the COPY command cannot be used to save files to other mounted volumes.
This option is enabled by default, and there is rarely a reason to turn it off. Older versions of NetForms did not support Mac OS alias resolution, so allowing access outside the Root Folder provided a means of accessing other volumes. Now, however, you can access any folder on any mounted volume simply by placing an alias of the folder inside the Root Folder.
On the other hand, there are very good reasons for leaving it on. When you permit NetCloak Pro to access files outside the Root Folder, any file, even those within the System Folder, can be opened, read, or overwritten using the appropriate FDML commands. This is particularly dangerous if you provide FTP upload abilities to your users, or if you disable some of the other security settings described below. In such a situation, a malicious user with knowledge of FDML syntax could upload or submit an FDML file which contained directives instructing NetCloak Pro to overwrite your System or Finder files with meaningless garbageÑ thus quickly turning your server into an expensive paperweight.
Prohibit fdml tags in form fieldsÑ When this option is checked, then NetCloak Pro pre-screens all input form data and rejects any post that contains any FDML tags.
Again, this setting exists to prevent malicious users with knowledge of FDML syntax from submitting data that creates a new FDML file on your server, which could be written to return the contents of sensitive files via the user's Web browser.
FDML files must have suffixÑ This security setting causes NetCloak Pro to double-check the file suffix of FDML files before processing their contents. If the suffix of the file does not match the configured value (which defaults to ".fdml" and rarely need to be changed), then NetCloak Pro merely returns an error message to the user who submitted the form.
Early version of NetForms would process any file containing FDML commands which was specified in a form's ACTION attribute. This posed a potential security risk because a hacker could enter FDML commands into documents saved with an ".html" or ".txt" extension, and NetForms could then be used to retrieve files from the web server using that new, bogus, FDML file. Enabling this option causes NetCloak Pro to reject any FDML file not ending with the configured suffix. By default, the suffix is set to ".fdml". Obviously, the configured suffix should not be used as the suffix of any files created via CREATEDOC or TEXTSTORE directives.
Form and FDML must be on same serverÑ When you enable this security setting, you are preventing other web sites from "hijacking" your form.
Because the URL that defines the location of your FDML file, such as "http://your.server.com/Recipes/Recipe.FDML", can be accessed from anywhere on the Internet, any web site could duplicate or copy the HTML form which provides user input to your FDML. Then, anyone using that form on the other web site would submit data to your server to be processed by NetCloak Pro. This is known as "hijacking" your form.
This can cause many undesirable effects, such as skewing survey data collected via the form, or overloading your web server with more traffic than it was designed to withstand.
When this option is enabled, NetCloak Pro verifies that the HTML form used to submit data and the FDML file which will process the data reside on the same machine. If they do not, an error message is returned to the web browser and the form data is not processed.
There are a few configuration items outside of NetCloak that have an effect on how some NetCloak commands behave. These affect DOMAIN command parameters and how NetCloak commands display dates and times.
Most web servers support an option to look up the domain name corresponding to the client IP address for each connection. Such an option is usually named something like "Look up client names", "Perform DNS lookups" or "Use DNS". This option affects how the server passes the client address to NetCloak, which affects the behavior of NetCloak's DOMAIN commands. When it is off, the server passes the TCP/IP address of the client to NetCloak without trying to resolve the machine name. When it is on, it will pass the host name instead.
The HIDE, SHOW and INSERT_DOMAIN commands in NetCloak will use the address as it is passed from the server. This means that when DNS lookup is turned on in the server, the INSERT_DOMAIN command will insert the hostname (like "www.maxum.com") and when it is turned off it will insert the IP address (like "198.85.68.67"). Likewise, you will have to use appropriate parameters in the HIDE_DOMAIN command depending on whether NetCloak
The INSERT_TIME and INSERT_DATE commands will display the time and date using the format selected in the Date & Time control panel on the server. Also, parameters to the HIDE_DATE and SHOW_DATE commands must match the short date format set in the Date & Time control panel. Make sure that the time and date formats are set according to how you would like them displayed on your pages. Since the date and time functions of NetCloak rely on the server's system clock, make sure the time and date are accurate.
| Copyright © 1996-2000 Maxum Development Corporation http://www.maxum.com/ |
Previous |
Next Contents |