If you use a trailing / (slash) in defining an alias, the requests that are capable of accessing the aliased directory also need to contain a trailing /

The AliasMatch directive is similar to the Alias directive, except that it can make use of regular expressions Syntax: AliasMatch regex path Context: Server config, virtual host For example, the following directive matches

The Redirect directive redirects a URL request to another URL If you have moved a section of your Web site to a new directory or even a new Web site, you can use this directive to ensure that people who have bookmarked the old site are still able to find it Syntax: Redirect [status_code] old_URL new_URL Context: Server config, virtual host, directory, per-directory access control file (htaccess) For example, the following directive redirects all URL requests containing the /data path to the new URL Therefore, requests for wwwyoursitecom/data/somefiletxt are redirected to wwwyour-new-sitecom/data/somefiletxt:

The Redirect directive has precedence over the Alias and ScriptAlias directives By default, the status code sent to the client is Temp (HTTP status code 302) If you want to specify a different status code, use the following:

Status Code Permanent Temp See other Gone What It Does Tells the client that the redirect is permanent The HTTP status code 301 is returned Returns a temporary redirect status (302) This is the default Returns a See Other status (303), indicating that the resource has been replaced Returns a Gone status (410) indicating that the resource has been permanently removed When this status is used, the URL argument should be omitted

You can provide valid HTTP status codes in numeric format as well If the status you provide is between 300 and 399, the new-URL must be present; otherwise, it must be omitted You may wonder about the use of different status codes In the future, clients may be smart enough to recognize the status codes in a more meaningful manner For example, if a proxy server receives a permanent redirect status code, it can store this information in a cache so that it can directly access the new resource in a later request

The RedirectMatch directive is similar to the Redirect directive, but it accepts regular expressions instead of the simple old URL Syntax: RedirectMatch [status_code] regex URL Context: Server config, virtual host For example, the following directive redirects all requests that end with htm to an

As an example of how this would work, the following request:

is redirected to:

The RedirectTemp directive is similar to the Redirect directive It lets the client know that the redirect is only temporary Note that the Redirect directive also produces a temporary status by default Syntax: RedirectTemp old_URL new_URL Context: Server config, virtual host, directory, per-directory access control file (htaccess)

The RedirectPermanent directive is similar to the Redirect directive It lets the client know that the redirect is permanent Note that the Redirect directive produces a temporary status by default, but you can use the status code 301 or the keyword permanent, as the status does, the same as this directive

Syntax: RedirectPermanent old_URL new_URL Context: Server config, virtual host, directory, per-directory access control file (htaccess)

The ScriptAlias directive creates an alias for the physical directory path Additionally, any filename supplied in the request is treated as a CGI script, and the server attempts to run the script Syntax: ScriptAlias alias physical_directory_path Context: Server config, virtual host For example, the following directive can be used to process a request such as www niteccom/cgi-bin/somescriptpl The server tries to run somescriptpl if proper permission is verified Note that the ScriptAlias directory is not browseable:

ScriptAlias /cgi-bin/ /www/nitec/public/cgi-bin/