www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim Shoppa <sho...@trailing-edge.com>
Subject general/9639: Apache will not deliver a "Last-modified:" header of before Jan 1, 1970
Date Tue, 29 Jan 2002 19:50:18 GMT

>Number:         9639
>Category:       general
>Synopsis:       Apache will not deliver a "Last-modified:" header of before Jan 1, 1970
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Tue Jan 29 12:00:01 PST 2002
>Originator:     shoppa@trailing-edge.com
>Release:        1.3.22
Linux 2.4.16
I have many files with datestamps from before Jan 1, 1970.  Apache
will not serve them with their true datestamps in the "Last-modified:"

Same is true for CGI scripts which return "Last-modified:" dates from
before Jan 1, 1970; the header gets converted to Jan 1, 1970.

I know that internally Apache certainly carries around dates as seconds
since Jan 1, 1970, but many (most?) OS's are quite happy with datestamps
in the range 1903-2038 (i.e. 32-bit signed integer for # seconds offset
from the epoch.)


 [In order for any reply to be added to the PR database, you need]
 [to include <apbugs@Apache.Org> in the Cc line and make sure the]
 [subject line starts with the report component and number, with ]
 [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 ["Re: general/1098:").  If the subject doesn't match this       ]
 [pattern, your message will be misfiled and ignored.  The       ]
 ["apbugs" address is not added to the Cc line of messages from  ]
 [the database automatically because of the potential for mail   ]
 [loops.  If you do not include this Cc, your reply may be ig-   ]
 [nored unless you are responding to an explicit request from a  ]
 [developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]

View raw message