DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21500>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21500 access logs are not 100% sorted by time ------- Additional Comments From [EMAIL PROTECTED] 2003-11-17 05:52 ------- This bug is essentially the same as bug 10062. In a reply to that bug, the explanation was that the timestamp from when the request processing was *begun* is being used instead of the timestamp when it ended. THAT is the root of the problem. If the access log is using the beginning timestamp instead of the ending timestamp, this behavior is different from that of Apache 1.3 and is contrary to what Apache's own documentation states for both 1.3 and 2.0 regarding the timestamp in the access log: http://httpd.apache.org/docs-2.0/logs.html#accesslog It is important that the *ending* timestamp be used to keep logs in reasonably chronological order. It makes a huge difference when the request being served is for a file that is hundreds of megabytes and takes 7+ hours to serve over a slow link. It is also important to be able to match an error log message with the request that caused it. If the timestamps are very different, it makes it much more difficult to match request with error. So, using the beginning timestamp for the access log is definitely a bug, IMO. If you *absolutely insist* on changing this functionality, then please provide an option for backwards compatibility. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
