iTP Secure WebServer System Administrators Guide (Version 7.5+)

PutScript CGI-script-filename
The PutScript command indicates that the server will handle PUT requests, and it specifies the
location of the script that authenticates the client and performs any other necessary validation
functions.
The PutScript command overrides for specified regions any global specifications set for the
same items by the PutScript directive. For further information about the PutScript directive,
see “PutScript” (page 231).
Redirect [status] [-replace / replace-spec] target-url
The Redirect command tells the server to return the specifiedURL (target-url) for the requested
object. For example, if you moved HTML document /info/stats.html to /statsinfo.html
at a different host machine, you could use the following Redirect command to redirect all requests
for this document:
Region /info/stats.html {
Redirect http://www.widgets.com/statsinfo.html
}
The status variable indicates whether the specified redirection is temporary or permanent.
Accordingly, the value can be either temporary or permanent. When a request is satisfied by
redirection, the server returns a status code of 301 to the client if the requested file was moved
permanently, or a status code of 302 if the requested file was moved temporarily. If you omit this
variable from the command, the server behaves as if the redirect were temporary, returning a status
code of 302.
The -replace argument allows you to redirect requests for an entire directory. When you specify
this argument, the URL element specified by /replace-spec is removed from the front of the
requested URL. Then the remainder of the requested URL is appended to the target URL.
For example, you can use the following Redirect command to redirect requests for all the objects
under directory /info/stocks/* to the new location http://quote.widgets.com/stocks:
Region /info/stocks/* {
Redirect -replace /info/stocks
http://quote.widgets.com/stocks
}
RequiredFileExtension [-noexist] file-extension
The RequiredFileExtension command restricts the file extensions in URLs used to request
content the region. For example, you could use this command to prevent an ATP script from being
downloaded as text. The ability to restrict the file extension in the URL is especially important for
content in a /G or /E namespace, because stored files in those namespaces do not have real
extensions.
The -noexist argument allows you to control the error reported if a received URL has an incorrect
extension for the region. If you specify the option, the response to a request with an incorrect
extension is "file not found." If you omit the option, the response to a request with an incorrect
extension is "access denied."
The file-extension variable specifies the required extension. (Do not include a period in the
value.)
For example, the following command requires that all URLs starting with /G have the extension
.html. If the URL in the request has some other extension, the server returns an "access denied"
error to the browser:
Region /G* {
RequiredFileExtension html
}
The following command requires that all URLs starting with /G have the extension .html. If the URL
in the request has some other extension, the server returns a "file not found" error to the browser.
Region /G* {
RequiredFileExtension -noexist html
}
Region 239