Talk:Common Log Format
![]() | This article is rated Start-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||
|
Useful URLs to add
[edit]http://technet2.microsoft.com/WindowsServer/en/library/468e7ca4-fac8-4a5e-ab4f-5a2a2bbd7f9a1033.msp
- —Hobart 22:25, 9 March 2007 (UTC)
- Why is this useful? It's about "Windows Server 2003", there's nothing about "log formats" on this site. -- 2A03:3680:0:3:0:0:0:67 (talk) 23:24, 7 May 2013 (UTC)
Date format
[edit]Background: I went looking for the official format for the date field (specifically, I was trying to determine if a single-digit day would be a single character or preceded by a 0 or space. I realized that the Common Logfile Format does not actually define this detail. My question started because the nginx documentation simply states that the $time_local
variable is defined as "local time in the Common Log Format (1.3.12, 1.2.7)"[1]. After the Common Logfile Format, my first stop was the closest "relative" standard, i.e. the Extended Log File Format; however, the Date
directive uses no colon between the date and time, and the entries use a fully numeric format[2]. My next stops were the NCSA and Apache documentation, and they both document the syntax as it is stated in the article: %d/%b/%Y:%H:%M:%S %z
[3][4].
Issue to resolve: Given the ambiguity of the Common Logfile Format and it's closest relative and only application documentation to support a standard format, is this statement in the article actually valid without a qualification? Is there an un-cited reference that supports it? Does this issue deserve a discussion in the article?
[10/Oct/2000:13:55:36 -0700] is the date, time, and time zone that the request was received, by default in strftime format %d/%b/%Y:%H:%M:%S %z.
— TekWiz (talk) 13:34, 21 August 2017 (UTC)