Prev: DataBase Configuration --- Up: Configuration Directive Reference --- Next: Configuring What Is logged

Table Names

LogSQLTransferLogTable

LogSQLTransferLogTable table-name

Example: LogSQLTransferLogTable access_log_table

Context: virtual host

Defines which table is used for logging of Apache's transfers; this is analogous to Apache's TransferLog directive. table-name must be a valid table within the database defined in the LogSQLLoginInfo connection URI.

This directive is not necessary if you declare LogSQLMassVirtualHosting On, since that directive activates dynamically-named tables. If you attempt to use LogSqlTransferlogTable at the same time a warning will be logged and it will be ignored, since LogSQLMassVirtualHosting takes priority.

Requires unless LogSQLMassVirtualHosting is set to On

LogSQLCookieLogTable

LogSQLCookieLogTable table-name

Example: LogSQLCookieLogTable cookie_log

Default: cookies

Context: virtual host

Defines which table is used for logging of cookies. Working in conjunction with LogSQLWhichCookies, you can log many of each request's associated cookies to a separate table. For meaningful data retrieval the cookie table is keyed to the access table by the unique request ID supplied by the standard Apache module mod_unique_id.

You must create the table (see create-tables.sql, included in the package), or LogSQLCreateTables must be set to "on".

LogSQLHeadersInLogTable

LogSQLHeadersInLogTable table-name

Example: LogSQLHeadersInLogTable headers

Default: headers_in

Context: virtual host

Defines which table is used for logging of inbound headers. Working in conjunction with LogSQLWhichHeadersIn, you can log many of each request's associated headers to a separate table. For meaningful data retrieval the headers table is keyed to the access table by the unique request ID supplied by the standard Apache module mod_unique_id.

Note that you must create the table (see create-tables.sql, included in the package), or LogSQLCreateTables must be set to "on".

LogSQLHeadersOutLogTable

LogSQLHeadersOutLogTable table-name

Example: LogSQLHeadersOutLogTable headers

Default: headers_out

Context: virtual host

Defines which table is used for logging of outbound headers. Working in conjunction with LogSQLWhichHeadersOut, you can log many of each request's associated headers to a separate table. For meaningful data retrieval the headers table is keyed to the access table by the unique request ID supplied by the standard Apache module mod_unique_id.

Note that you must create the table (see create-tables.sql, included in the package), or LogSQLCreateTables must be set to "on".

LogSQLNotesLogTable

LogSQLNotesLogTable table-name

Example: LogSQLNotesLogTable notes-log

Default: notes

Context: virtual_host

Defines which table is used for logging of notes. Working in conjunction with LogSQLWhichNotes, you can log many of each request's associated notes to a separate table. For meaningful data retrieval the notes table is keyed to the access table by the unique request ID supplied by the standard Apache module mod_unique_id.

This table must be created (see create-tables.sql included in the package), or LogSQLCreateTables must be set to 'On'.

LogSQLMassVirtualHosting

LogSQLMassVirtualHosting flag

Example: LogSQLMassVirtualHosting On

Default: Off

Context: main server config

If you administer a site hosting many, many virtual hosts then this option will appeal to you. If you turn on LogSQLMassVirtualHosting then several things happen:

• the on-the-fly table creation feature is activated automatically

• the transfer log table name is dynamically set from the virtual host's name after stripping out SQL-unfriendly characters (example: a virtual host www.grubbybaby.com gets logged to table access_www_grubbybaby_com)

• which, in turn, means that each virtual host logs to its own segregated table. Because there is no data shared between virtual servers you can grant your users access to the tables they need; they will be unable to view others' data.

This is a huge boost in convenience for sites with many virtual servers. Activating LogSQLMassVirtualHosting obviates the need to create every virtual server's table and provides more granular security possibilities.

This is defined only once in the httpd.conf file.