IDC资讯中心
authname directive
syntax: authname auth-domain
context: directory, .htaccess
override: authconfig
status: core
this directive sets the name of the authorization realm for a directory. this realm is given to the client so that the user knows which username and password to send. authname takes a single argument; if the realm name contains spaces, it must be enclosed in quotation marks. it must be accompanied by authtype and require directives, and directives such as authuserfile and authgroupfile to work.
——————————————————————————–
authtype directive
syntax: authtype type
context: directory, .htaccess
override: authconfig
status: core
this directive selects the type of user authentication for a directory. only basic and digest are currently implemented. it must be accompanied by authname and require directives, and directives such as authuserfile and authgroupfile to work.
——————————————————————————–
bindaddress directive
syntax: bindaddress saddr
default: bindaddress *
context: server config
status: core
a unix® http server can either listen for connections to every ip address of the server machine, or just one ip address of the server machine. saddr can be
*
an ip address
a fully-qualified internet domain name
if the value is *, then the server will listen for connections on every ip address, otherwise it will only listen on the ip address specified.
only one bindaddress directive can be used. for more control over which address and ports apache listens to, use the listen directive instead of bindaddress.
bindaddress can be used as an alternative method for supporting virtual hosts using multiple independent servers, instead of using <virtualhost> sections.
see also: dns issues
see also: setting which addresses and ports apache uses
——————————————————————————–
bs2000account directive
syntax: bs2000account account
default: none
context: server config
status: core
compatibility: bs2000account is only available for bs2000 machines, as of apache 1.3 and later.
the bs2000account directive is available for bs2000 hosts only. it must be used to define the account number for the non-privileged apache server user (which was configured using the user directive). this is required by the bs2000 posix subsystem (to change the underlying bs2000 task environment by performing a sub-logon) to prevent cgi scripts from accessing resources of the privileged account which started the server, usually sysroot.
only one bs2000account directive can be used.
see also: apache ebcdic port
——————————————————————————–
clearmodulelist directive
syntax: clearmodulelist
context: server config
status: core
compatibility: clearmodulelist is only available in apache 1.2 and later
the server comes with a built-in list of active modules. this directive clears the list. it is assumed that the list will then be re-populated using the addmodule directive.
———————–
