Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Date: Tue, 12 Mar 2002 17:29:28 -0500
Message-Id: <200203122229.g2CMTSo26556@smtp-server.nc.rr.com>
From: Jeff Trawick <trawick@attglobal.net>
To: dev@httpd.apache.org
Subject: dumb questions on a couple of the current 2.0 showstoppers
Reply-to: trawick@attglobal.net

1)  * If any request gets to the core handler, without a flag that this 
      r->filename was tested by dir/file_walk, we need to 500 at the very 
      end of the ap_process_request_internal() processing.  This provides
      authors of older modules better compatibility, while still improving
      the security and robustness of 2.0.

    True or false: This refers to an issue where some broken module
                   causes the core dir walk to be skipped yet the
                   request gets to default handler.

    If true: Why is this a showstopper?  Broken modules cause all sorts
             of problems.  If this actually needs to be fixed, it can
             be fixed at any time.

    Either way: Any feedback on the comments that JimJag and I put in
                the STATUS file?

                Is this issue any more complicated than setting a flag
                in the last several "return OK" paths in
                ap_directory_walk() and in default_handler() to return
                HTTP_FORBIDDEN if the flag isn't set?

2)  * API changes planned for 2.0 that should happen before the
      GA release:
          * Free lists for bucket allocation
          * Pool allocator change

    Can anybody comment on the current status of either of these?  Is
    there work available for the masses to do?  Can we get the API
    changes committed Real Soon Now even if the new behavior isn't yet
    ready?

Thanks,

-- 
Jeff Trawick | trawick@attglobal.net
Born in Roswell... married an alien...