[ Pobierz całość w formacie PDF ]
.You can use only one TransferLog directive in the configuration file.DefaultIf you do not specify a TransferLog, the server assumes the following:TransferLog logs/access.logExamples" The following directive logs the transfers to the file logs/transfers in theServerRoot directory:TransferLog logs/tranfers" The following directive logs the transfers to the file /tmp/transfers:TransferLog /tmp/transfers" The following directive turns off transfer logging:TransferLog /dev/nullNote /dev/null is a special path known by the server.This path also works onnon-UNIX platforms.AgentLogThe AgentLog directive determines where the server records client software.The UserAgentheader, if present, is recorded in the format the client sends.If LogOptions is set toCombined, this directive does nothing.All clients can use this directive for statistical purposes and to track protocol violations.Thefirst whitespace-delimited word must be the software product name, with an optional slashand version designator.Other products that form part of the user agent can be written asseparate words.User AgentLog ExampleThe timestamp has the same format as in access.log.[02/Oct/1996:14:48:07 -0500] Mozilla/2.0 (Macintosh; I; 68K)[02/Oct/1996:15:01:29 -0500] Mozilla/3.0Gold (Win95; I)© National Instruments Corporation A-25 Internet Developers Toolkit for GAppendix A Configuration Directives[02/Oct/1996:18:23:51 -0500] Mozilla/2.0 (compatible; MSIE 3.0;Windows 95)[03/Oct/1996:15:47:17 -0500] Lynx/2.3.7 BETA libwww/2.14SyntaxAgentLog filefile is the name of the file to which user agents log information, either a full pathname or apartial pathname relative to the ServerRoot.You can use only one AgentLog directive in the configuration file.DefaultIf you do not specify an AgentLog, the server assumes the following:AgentLog logs/agent.logExamples" The following directive logs user agents to the file logs/agents in the ServerRootdirectory:AgentLog logs/agents" The following directive logs user agents to the file /tmp/agents:AgentLog /tmp/agents" The following directive turns off user agent logging:AgentLog /dev/nullNote /dev/null is a special path known by the server.This path also works onnon-UNIX platforms.RefererLogThe RefererLog directive determines where the server records refer.The Referer header, ifpresent, is recorded in the following format:[Time Stamp] URI -> Documentwhere URI is the Universal Resource Identifier for the document that references the server,and Document is the virtual path to the requested document.If LogOptions is set toCombined, this directive does nothing.Internet Developers Toolkit for G A-26 © National Instruments CorporationAppendix A Configuration DirectivesUser RefererLog ExampleThe timestamp has the same format as in access.log.[02/Oct/1996:18:22:08 -0500] http://cerberus/htdocs/ ->/htdocs/images/logo.gif[02/Oct/1996:18:22:11 -0500] http://cerberus/htdocs/ ->/htdocs/config/config.htm[02/Oct/1996:18:22:12 -0500]http://cerberus/htdocs/config/config.htm ->/htdocs/config/access/access.htmSyntaxRefererLog filefile is the name of the file to which referers are logged, either a full pathname or a partialpathname relative to the ServerRoot.You can use only one RefererLog directive in the configuration file.DefaultIf you do not specify a RefererLog, the server assumes the following:RefererLog logs/referer.logExamples" The following directive logs referers to the file logs/referers in the ServerRootdirectory:RefererLog logs/referers" The following directive logs referers to the file /tmp/referers:RefererLog /tmp/referers" The following directive turns off referer logging:RefererLog /dev/nullNote /dev/null is a special path known by the server.This path also works onnon-UNIX platforms
[ Pobierz całość w formacie PDF ]