Hello all!
There are a lot of programs, which analyze access log files and
generates statistics reports.
Current most detailed log format ("combined") doesn't contain some
interesting fields
(which may be analyzed by such systems).
Yes, developers of these systems
may ask users to define custom log format,
but in my opinion global standardization way is better.
I think it will be better to define _standard_ "full" log format
and add it into standard configuration file
(which is included in installation package)
near definition of "combined", "access", "referer" and "agent" formats.
I think next fields are useful:
(In my opinion, all of them have to be included.
If somebody doesn't need some of them, he(or she) can ignore such ones)
%t: Time, in common log format time format (standard english format)
%a: Remote IP-address
%h: Remote host
%l: Remote logname (from identd, if supplied)
%A: Local IP-address
%p: The canonical Port of the server serving the request
%v: The canonical ServerName of the server serving the request.
%V: The server name according to the UseCanonicalName setting.
%U: The URL path requested, not including any query string.
%q: The query string (prepended with a ? if a query string exists,
otherwise an empty string)
%f: Filename
%r: First line of request
%H: The request protocol
%m: The request method
%{User-Agent}i: Signature of user agent.
%{Referer}i: Referer document URL
%P: The process ID of the child that serviced the request.
%{cookie}n: User tracking cookie
%u: Remote user (from auth; may be bogus if return status (%s) is 401)
%s: Status. For requests that got internally redirected, this is the
status of the *original* request
%>s: Last status for requests that got internally redirected.
%B: Bytes sent, excluding HTTP headers.
%D: The time taken to serve the request, in microseconds.
%{Content-type}o: mime-type of response content
%X: Connection status when response is completed.
Sincerely yours,
Leonid Antonenkov
Email: [EMAIL PROTECTED]
ICQ UIN: 23637980
