| Description
|
Enter a name that differentiates this rule
from others you create.
|
| Type of Rule
|
Choose one:
- Directory -- To allow a server file-system directory to be accessed
by a URL path.
- Redirection -- Resource identified by the URL has been moved to
a different location or Web site.
- Substitution -- To replace a string in the URL with another string.
- HTTP response header -- To add an Expire header or custom headers
to HTTP responses that match specified URL patterns and response codes.
- Override session authentication -- To set up basic authentication
for a specific Web site when session-based authentication is enabled
for the server.
|
| Incoming URL pattern
|
Pattern that describes the URLs affected by
this rule.
If you are defining many rules, specify the longest
unique pattern for each rule. Do not include http or the host name
in the pattern.
|
| Redirect to this URL
|
(Redirection only) Enter the new URL location.
If the URL pattern in this field starts with a slash, the rule is
treated as internal redirection. Otherwise, the rule is assumed to
be external redirection.
The pattern for an external redirection
needs to start with an Internet protocol string that the browser understands,
such as http: or ftp.
|
| Send 301 Redirect
|
(Redirection only) Available only when you
have specified values for both Incoming URL pattern and Redirect
to this URL. Domino normally sends a redirect http return
code of 302, indicating that the redirect is only temporary. Selecting
Yes in this check box instead sends a return code of 301, indicating
that the redirect should be permanent, and causing the browser to
remember the redirect URL.
|
| Replacement pattern
|
(Substitution only) Enter the string that replaces
the matching part of the incoming URL.
|
| Target server directory
|
(Directory only) Enter the file-system directory
path being mapped. This can be specified as a fully-qualified path
or a path relative to the data directory. If you want to map a directory
that isn't under the Domino data directory, specify the fully qualified
path.
|
| Access level
|
(Directory only) Choose one:
- Read access -- To allow browser users to read files from the directory
are displayed in the browser or downloaded. When a user requests a
file from the directory, the server sends the contents of the file
back to the browser.
- Execute access -- To allow browser users to load and run CGI programs
in the directory. The server relays the output from the program to
the browser.
|
| HTTP response codes
|
(HTTP Response Header only) Enter the HTTP
response codes to which you want your response headers applied.
|
| Expires header
|
(HTTP Response Header only) Choose one:
- Don't add header -- Files in the directory are displayed in the
browser or downloaded.
- Add header only if application did not -- Files in the directory
are CGI files to be executed on the server.
- Always add header (override application's header)
Note: If you choose to add a header, you must specify an expiration
period -- either by specifying the number of days for which you want
to enable this header, or a date after which you want to disable this
header.
|
| Custom header
|
(HTTP Response Header only) For each custom
header you want to use, specify:
- Name: The name of the response header.
- Value: The value of the response header.
- Override: Override application's header.
- Applies to: Whether it applies to HTTP, HTTPS, or All (HTTP and HTTPS).
|