httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From r..@engelschall.com (Ralf S. Engelschall)
Subject [STATUS] Apache 1.2.2 (Sun 3-Aug-1997 12:22 MET DST)
Date Sun, 03 Aug 1997 10:22:29 GMT

STATUS for Apache 1.2.2 
=======================

Patches already committed: 
(see ``src/CHANGES'' file for more details)

    o PR#813,814: obscure proxy stuff (case on Host:, etc.)
    o PR#797: fix mod_include logging a little...
    o PR#832: solaris -HUP problem with slack fd
    o PR#378 part 1: Fix handling of request body in core
    o API Symbol APACHE_RELEASE provides numeric form
    o PR#094: revisited
    o PR#848: treat <files> container like others in mod_info. 
    o PR#815: wrong length in get_client_block() 
    o PR#875: MSIE 4.0 PR2 workaround ("downgrade-1.0")
    o PR#421,868: mod_auth_anon logs multiple times
    o PR#777/+++: final sync of mod_rewrite for Apache 1.2.2
    o mod_include: handle_else was being used to handle endif. 
    o merging in of all essential documentation changes from 1.3
    o merging of updated mod_rewrite documentation after final sync
    o PR#748: mod_imap infinite loop for references above serverroot
    o fix for case where multiple <Directory>s match and all are applied 

Patches available: 
(see appended MIME-part ``patches.txt'' for diff snippets)

    o [patch.solaris]
      Dean's patch for the solaris which superseeds
      "PR#832: solaris -HUP problem with slack fd"
      It moves ap_slack after all of the rest of the socket initialization, I
      think the critical steps are the SO_REUSEADDR and the listen().  It also
      blocks SIGHUP and SIGUSR1 during restart, which makes it pass a "while
      1; kill -HUP or kill -USR1" test. 
      Status: Dean +1
      => ** THIS PATCH WORKED FOR DEAN NOW, CAN ANYBODY ELSE ALSO TEST IT? **

    o [patch.chunkerr]
      Dean's "[PATCH] 1.2.2: obscure chunking error":
      <Pine.LNX.3.95dg3.970729000353.17653A-100000@benchlark.arctic.org>
      While chunking, it is possible to exit bwrite() or bflush() without
      having started the next chunk.  It should only happen when there's a
      write error ... but in some cases it would return without setting the
      error flags.
      Status: Dean +1, RSE +0 
      => ** STILL NEEDS TESTING OR WE IGNORE IT FOR 1.2.2! **

                                       Ralf S. Engelschall
                                       rse@engelschall.com
                                       www.engelschall.com

Mime
View raw message