httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From c...@hyperreal.org
Subject cvs commit: apachegroup-site Y2K.html
Date Fri, 03 Sep 1999 20:03:07 GMT
coar        99/09/03 13:03:07

  Added:       .        Y2K.html
  Log:
  	Okey, here it is -- the FAQ answer nicely packaged on an
  	ASF page.
  
  Revision  Changes    Path
  1.1                  apachegroup-site/Y2K.html
  
  Index: Y2K.html
  ===================================================================
  <!doctype html public "-//W3C//DTD HTML 3.2 Final//EN">
  <html>
   <head>
    <title>Apache HTTP Server Y2K Readiness Statement</title>
   </head>
  <!-- Background white, links blue (unvisited), navy (visited), red (active) -->
   <body
    bgcolor="#ffffff"
    text="#000000"
    link="#0000ff"
    vlink="#000080"
    alink="#ff0000"
   >
    <table width="100%" border="0">
     <tr>
      <td valign="top">
       <p><a href="http://www.apache.org/"
          ><img src="images/asf_logo.gif"
            alt="The Apache Software Foundation"
            border="0" width="387" height="100"></a>
       </p>
       <p>&nbsp; </p>
      </td>
     </tr>
    </table>
  
    <table width="100%" border="0">
     <tr>
      <td width="160" valign="top" align="center">
       <p>
       <b><a href="FAQ.html">FAQ</a><br>
          <a href="news.html">News &amp; Status</a><br>
          <a href="mailinglists.html">Mailing Lists</a><br>
          <a href="contributing.html">Contributing</a><br>
          <a href="contact.html">Contact Info</a><br>
          <a href="credits.html">Credits</a><br>
       </b>
       <hr width="50%" size="4">
       <b><a href="bylaws.html">Bylaws</a><br>
          <a href="members.html">Members</a><br>
          <a href="board/">Board of Directors</a><br>
          <a href="records/">Public Records</a><br>
       </b>
       <hr width="50%" size="4">
       <a href="projects.html"><font size="-1">ASF Projects:</font></a><br>
       <b><a href="../httpd.html">Apache Server</a><br>
          <a href="http://jakarta.apache.org/">Jakarta</a><br>
          <a href="http://java.apache.org/">Java-Apache</a><br>
          <a href="http://perl.apache.org/">mod_perl</a><br>
          <a href="http://php.apache.org/">mod_php</a><br>
          <a href="conferences.html">Conferences</a><br>
          <a href="./">Foundation</a><br>
       </b>
       </p>
      </td>
      <td valign="top">
  
       <h1 align="center">Apache HTTP Server Year-2000 Readiness</h1>
       <dl>
        <dd>
         <p>
         <strong>Q: Is Apache Year 2000 compliant?</strong>
         </p>
  
         <p>
         Yes, Apache is Year 2000 compliant.
         </p>
  
         <p>
         Apache internally never stores years as two digits.
         On the HTTP protocol level RFC1123-style addresses are generated
         which is the only format a HTTP/1.1-compliant server should
         generate. To be compatible with older applications Apache
         recognizes ANSI C's <code>asctime()</code> and
         RFC850-/RFC1036-style date formats, too.
         The <code>asctime()</code> format uses four-digit years,
         but the RFC850 and RFC1036 date formats only define a two-digit year.
         If Apache sees such a date with a value less than 70 it assumes that
         the century is <samp>20</samp> rather than <samp>19</samp>.
         </p>
  
         <p>
         Although Apache is Year 2000 compliant, you may still get problems
         if the underlying OS has problems with dates past year 2000
         (<em>e.g.</em>, OS calls which accept or return year numbers).
         Most (UNIX) systems store dates internally as signed 32-bit integers
         which contain the number of seconds since 1<sup>st</sup> January 1970,
so
         the magic boundary to worry about is the year 2038 and not 2000.
         But modern operating systems shouldn't cause any trouble
         at all.
         </p>
  
         <P>
         Users of Apache 1.2.x should upgrade to a current version of Apache 1.3
         (see
         <a href="http://www.apache.org/docs/new_features_1_3.html#misc"
         >year-2000 improvements in Apache 1.3</a>
         for details).
         </p>
  
         <p>
         The Apache HTTP Server project is an open-source software product of
         the Apache Software Foundation.  The project and the Foundation
         <b>cannot</b> and <b>does not</b>  offer legal assurances
regarding
         any suitability of the software for your application.  There are
         several commercial Apache support organizations and derivative
         server products available that may be able to stand behind the
         software and provide you with any assurances you may require.
         You may find links to some of these vendors at
         <samp>&lt;<a href="http://www.apache.org/info/support.cgi"
                   >http://www.apache.org/info/support.cgi</a>&gt;</samp>.
         </p>
  
         <p>
         The Apache HTTP server software is distributed with the following
         disclaimer, found in the software license:
         </p>
  
         <pre>
    THIS SOFTWARE IS PROVIDED BY THE APACHE GROUP ``AS IS'' AND ANY
    EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
    IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
    PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL THE APACHE GROUP OR
    ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
    SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
    NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
    LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
    HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
    STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
    ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
    OF THE POSSIBILITY OF SUCH DAMAGE.
         </pre>
        </dt>
       </dl>
      </td>
     </tr>
    </table>
  
   </body>
  </html>
  
  
  

Mime
View raw message