APACHE (6)

5.1.2AuthDBMUserFile syntax: AuthDBMUserFile file name is used in directory ,. htaccess requirement: AuthConfig status: Expansion Module: mod_auth_dbmAuthDBMUserFile: This file sets the name of the DBM file used for verification, including the list of users and passwords. The file name is the absolute tag of the user File: Apache 5.1.2 AuthDBMUserFile

Syntax: AuthDBMUserFile file name
Used for: directory,. htaccess
Requirement: AuthConfig
Status: expanded
Module: mod_auth_dbm

AuthDBMUserFile is set as the DBM file name used for verification.
List of users and passwords. The file name is the absolute path of the user file.

This file is based on the user name. The user-end value is crypt () encrypted
The password, followed by a selective colon and random information. The server will ignore
These colons and data.

Security: ensure that AuthDBMUserFile is stored outside the server's file tree; do not store it
Put it in the directory to be protected. Otherwise, the client will be able to download AuthDBMUserFile.

See AuthName, AuthType, and AuthDBMGroupFile.


5.2 mod_cookies module

This module is included in the mod_cookies.c file and will not be compiled by default.
Go. It provides Netscape (TM) cookies. This module does not have a description file.


5.2.1 CookieLog

Syntax: CookieLog file name
Used for: server config, virtual host
Status: Lab
Module: mod_cookies

CookieLog: specifies the name of the file used to record cookies. File name
Is the relative directory of ServerRoot.


5.3 mod_dld module

This module is included in the mod_dld.c file and will not be compiled by default.
It provides the ability to load executable files and modules to the server at startup, using GNU dld
Library.


5.3.1 summary

This selective dld module is used as a proof of concept (proof-of-concept ).
Program code, which loads other modules to the server as configured by itself (only for the first time)
So far, re-reading the configuration file does not affect the loaded modules.
Dynamic link library (DLD ). It is not compiled by default, because not everyone has
DLD, but I can try it. (Note the last few words ).

Note that for some reason, LoadFile/lib/libc. a seems necessary.

Note: When the server starts, the DLD needs to read the symbol table outside the server program;
If the server cannot find its own program code at startup, these commands will fail.


5.3.2 LoadFile

Syntax: LoadFile file name...
Used in: server config
Status: Lab
Module: mod_dld

LoadFile: this command links the target file or library named when the server starts;
This is an extra code that may be required to load some modules. The file name is relative
For ServerRoot.


5.3.3 LoadModule

Syntax: LoadModule module file name
Used in: server config
Status: Lab
Module: mod_dld

The LoaddModule command links the file name of the target file or library and
List of modules added to use. The module is an external parameter of the module in the medium state of the file.
. For example:

LoadModule ai_backcompat_module modules/mod_ai_backcompat.o
LoadFile/lib/libc.

Load the modules in the modules subdirectory of ServerRoot.


5.4 mod_log_agent module

This module is included in the mod_log_agent.c file and will not be compiled by default.
Go in. It provides the recording function of the client user program.


5.4.1 AgentLog

Syntax: AgentLog file-pipeline
Default: AgentLog logs/agent_log
Used for: server config, virtual host
Status: expanded
Module: mod_log_agent

The AgentLog command sets the name of the file requested by the server to log in. its content is
UserAgent header. FILE-pipeline is one of these:


File name
A file name relative to ServerRoot

'|' Follows a command
Procedures for receiving reference record information from standard input. Note that
If the server inherits the RefererLog settings, it will not start a new program.


Security: If a program is used here, it will be executed as the user starting httpd.
If the server is started by the root user, this program is executed by the root user.
Program Security.


This command is provided to be compatible with NCSA 1.4.


5.5 mod_log_config module

This module is included in the mod_log_config.c file and will not be compiled by default.
Go in. It allows you to record requests to the server in a format specified by the user.


5.5.1 summary

This is an experimental module that implements the TransferLog command (similar to the general record
The same module), and another command, LogFormat. I will not be surprised by any errors.

The LogFormat parameter is a string that can contain the text to be copied to the record, and
The '%' command is as follows:

%... H: remote host
%... L: remote check-in name (known from identd, if
Supported)
%... U: Remote User (according to auth, if the status of the return is
If (% S) is 401, there is a possibility of counterfeiting)
%... T: time, General Time record format
%... R: The first line of the request
%... S: status. Used in case of an internal re-import request, this is
{F original} request status --- %...> s is
Last.

%... B: The Sent bitkey.
%... {Foobar} I: Foobar content: the content of the request to be sent to the client
Header line.
Content of %... {foobar} o: Foobar: header row in reply

'...' Can be completely omitted (e.g. "% h % u % r % s % B"), or it can
Indicates the condition to contain a project (if this condition is not met, it will be replaced)
. Note that the % r, %... I, and %... o operations on the string are not separated.
(No escaping saved Med); some people with good memory may remember that I think this is not
A good idea. until now, I still catch a cold on it, but I need to see how to use '%... I'
It is very difficult to 'do the correct thing' unless we URL-escape everything and use CLF
Interrupt them.

The condition form is a list of HTTP status codes, which may or may not exist '! 'Leading
. Therefore, '% 400,501 {User-agent} I' records the User-agent. only the error status is correct.
400 and 501 (incorrect request, not implemented); '%! 200,304,302 {Referer} I'
Referer record: used for all requests that do not return normal status.

The default LogFormat is CFL.

The idea of working with a VM is as follows: the VM can have its own LogFormat
Or its own TransferLog. If it does not have its own LogFormat, it starts from
Main server inheritance. If it does not have its own TransferLog, it will write the same description
Descriptor (meaning the same program '| ).



The above is taken from PHPUSER. COM