|
These are the settings for the
"default" virtual server that handles all requests not covered
otherwise. These settings will not be taken over by virtual servers and
have to be set accordingly in their configuration block. If such a
setting doesn't show up in the
virtual servers definition block it will not be used. Don't forget that
the [-Referer] block is also considered to be a special setting and
won't be inherited.
- redirect
Takes a string that specifies the starting part of the target of the
302 type redirect. The string may not end with a "/" and it should
start with for example "http://" to form a complete address. An example
would be:
redirect="http://www.yourserver.org/myfolder";
If the server receives a path "/pictures/smg.gif" it will then create
"http://www.yourserver.org/myfolder/pictures/smg.gif" and use that in
the location line of the 302 response. The response body will contain a
simple html page containing a hyperlink with target and name to the
location in case the 302 doesn't work for some reason.
If a referer list is specified it will be used. Additional specified
headerlines will be used also, but all other settings will be ignored.
- referer_policy
Defines the way the referers listed in the [-Referer] list are interpreted.
Valid values are
"deny" and "allow", default is "allow". Any value but "deny" is
interpreted as "allow". If "referer_policy=allow" is set, then
listed referers are allowed, others are rejected. If
"referer_policy=deny" is set, then listed referers are rejected and
unknown
ones allowed.
- no cache
This is a flag and takes no values. If this is found in a virtual
server or the default server definition, the cache won't be used for
incoming requests. That's for people that have a VS providing for
example huge amounts of seldomly used files who want to preserve the
cache for the other VSs. The default is to use the global cache
setting.
|