APACHE 2.4 STATUS: -*- mode: text; coding: utf-8 -*- Last modified at [$Date$] The current version of this file can be found at: * http://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x/STATUS Documentation status is maintained separately and can be found at: * docs/STATUS in this source tree, or * http://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x/docs/STATUS The current development branch of this software can be found at: * http://svn.apache.org/repos/asf/httpd/httpd/trunk Consult the following STATUS files for information on related projects: * http://svn.apache.org/repos/asf/apr/apr/trunk/STATUS * http://svn.apache.org/repos/asf/apr/apr/branches/1.4.x/STATUS * http://svn.apache.org/repos/asf/apr/apr-util/branches/1.4.x/STATUS Patches considered for backport are noted in their branches' STATUS: * http://svn.apache.org/repos/asf/httpd/httpd/branches/2.0.x/STATUS * http://svn.apache.org/repos/asf/httpd/httpd/branches/2.2.x/STATUS * http://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x/STATUS Release history: [NOTE that x.{odd}.z versions are strictly Alpha/Beta releases, while x.{even}.z versions are Stable/GA releases.] 2.4.6 : Tagged on July 15, 2013. 2.4.5 : Tagged on July 11, 2013, not released. 2.4.4 : Tagged on February 18, 2013. Released Feb 25, 2013 2.4.3 : Tagged on August 17, 2012. Released Aug 18, 2012 2.4.2 : Tagged on April 5, 2012. Released Apr 17, 2012. 2.4.1 : Tagged on February 13, 2012. Released Feb 21, 2012. 2.4.0 : Tagged on January 16, 2012, not released. 2.3.16 : Tagged on December 15, 2011. 2.3.15 : Tagged on November 8, 2011. Released Nov. 15, 2011. 2.3.14 : Tagged on August 1, 2011. Released Aug. 9, 2011. 2.3.13 : Tagged on June 28, 2011, not released. 2.3.12 : Tagged on May 11, 2011. Released May 23, 2011. 2.3.11 : Released as Beta on March 7, 2011. 2.3.10 : Tagged on December 13, 2010. Released Dec 21, 2010. 2.3.9 : Tagged on November 23, 2010, not released. 2.3.8 : Tagged on August 24, 2010. 2.3.7 : Tagged on August 19, 2010, not released. 2.3.6 : Released on June 21, 2010. 2.3.5 : Released on January 26, 2010. 2.3.4 : Released on December 8, 2009. 2.3.3 : Tagged on November 11, 2009, not released. 2.3.2 : Tagged on March 23, 2009, not released. 2.3.1 : Tagged on January 2, 2009, not released. 2.3.0 : Tagged on December 6, 2008, not released. Contributors looking for a mission: * Just do an egrep on "TODO" or "XXX" in the source. * Review the bug database at: http://issues.apache.org/bugzilla/ * Review the "PatchAvailable" bugs in the bug database: https://issues.apache.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Apache+httpd-2&keywords=PatchAvailable After testing, you can append a comment saying "Reviewed and tested". * Open bugs in the bug database. * See also the STATUS file in the docs/ directory, which lists documentation-specific TODO items. CURRENT RELEASE NOTES: * Forward binary compatibility is expected of Apache 2.4.x releases, such that no MMN major number changes will occur after 2.4.1. Such changes can only be made in the trunk. * All commits to branches/2.4.x must be reflected in SVN trunk, as well, if they apply. Logical progression is commit to trunk then merge into branches/2.4.x, as applicable. RELEASE SHOWSTOPPERS: PATCHES ACCEPTED TO BACKPORT FROM TRUNK: [ start all new proposals below, under PATCHES PROPOSED. ] PATCHES PROPOSED TO BACKPORT FROM TRUNK: [ New proposals should be added at the end of the list ] * core, mod_ssl: Lift the restriction that prevents mod_ssl taking full advantage of the event MPM. Enable the ability for a module to reverse the sense of a poll event from a read to a write or vice versa. trunk patches: http://svn.apache.org/r1470679 http://svn.apache.org/r1477094 2.4.x patch: http://people.apache.org/~minfrin/httpd-event-ssl.patch +1: minfrin, jim -0.5: sf: I would prefer if this sat in trunk for a few months first to receive more testing. * core: Add pre_htaccess hook. trunk patch: http://svn.apache.org/r1389339 2.4.x patch: trunk patch works modulo CHANGES and mmn bump +1: minfrin, jim trawick: I like sf's idea on the list for a different API to solve the same problem. We shouldn't proceed with this patch. Alternate proposal: core: Add open_htaccess hook. trunk patch: http://svn.apache.org/r1389339 http://svn.apache.org/r1498880 2.4.x patch: http://people.apache.org/~sf/open_htaccess_hook.patch +1: sf, jorton, +0.5: jj: I would prefer if this sat in trunk for a few months first to receive more testing. +/-0: trawick: I would prefer if Steinar verifies that it is fine for him (however simple that verification would be). There's no need to proceed until he is ready to use it anyway. * core: Stop the HTTP_IN filter from attempting to write error buckets to the output filters trunk patch: https://svn.apache.org/viewvc?view=revision&revision=1482522 2.4.x patch: trunk patch works modulo CHANGES and ap_mmn +1: jim * mod_proxy: support Unix domain sockets trunk patch: https://svn.apache.org/viewvc?view=revision&revision=1451633 https://svn.apache.org/viewvc?view=revision&revision=1451905 https://svn.apache.org/viewvc?view=revision&revision=1451921 https://svn.apache.org/viewvc?view=revision&revision=1452259 https://svn.apache.org/viewvc?view=revision&revision=1453981 https://svn.apache.org/viewvc?view=revision&revision=1501913 2.4.x patch: trunk patch works modulo CHANGES, ap_mmn, and doc note to include version note +1: jim, druggeri druggeri note: Fails as a BalancerMember, FWIW * mod_proxy: Ensure network errors detected by the proxy are returned as 504 Gateway Timout as opposed to 502 Bad Gateway trunk patch: https://svn.apache.org/viewvc?view=revision&revision=1480058 2.4.x patch: trunk patch works modulo CHANGES +1: -1: rpluem: This change is still disputed. See http://mail-archives.apache.org/mod_mbox/httpd-dev/201305.mbox/%3C1B16B9E3-87BA-4EEF-939C-7C7313B54714%40gbiv.com%3E * mod_proxy: save DNS lookups trunk patch: https://svn.apache.org/viewvc?view=revision&revision=1462269 https://svn.apache.org/viewvc?view=revision&revision=1463455 2.4.x patch: trunk patch works +1: jim, druggeri * mod_socache_shmcb.c: Remove arbitrary restriction on shared memory size previously limited to 64MB. trunk patch: http://svn.apache.org/r1493921 http://svn.apache.org/r1493925 2.4.x patch: trunk patch works modulo CHANGES +1: minfrin, jim sf notes: I think a number of variables need to be changed from int to apr_size_t, including subcache_size, subcache_data_offset, subcache_data_size, total, cache_total. AIUI, especially cache_total starts to go wrong if the cache gets larger than 4GB (UINT_MAX). Maybe set the limit at MIN(APR_SIZE_MAX,UINT_MAX) until this is fixed? minfrin: Surely we should just fix these unsigned ints? Not sure what value there would be in trying to bake in an arbitrary limit in the mean time when we can just fix the underlying problem instead. jj: Agree w/ minfrin * modules: Fix some compiler warnings. trunk patch: http://svn.apache.org/r1500345 http://svn.apache.org/r1500362 http://svn.apache.org/r1500423 http://svn.apache.org/r1500483 http://svn.apache.org/r1500519 2.4.x patch: trunk patches work +1: fuankg comments: jj: In general, casts are sometimes used to "hide" problems that exist, esp when using the incorrect data types... Are these casts safe? fuankg: replied to list with further details about patches. * mod_cache: fill in APLOGNO value trunk: http://svn.apache.org/r1481396 http://svn.apache.org/r1502665 2.4.x patch: trunk works +1 covener, fuankg * mod_deflate: Improve error detection when decompressing request bodies with trailing garbage: handle case where trailing bytes are in the same bucket. trunk: http://svn.apache.org/r1502772 2.4.x patch: trunk works (minus log-message-tags) +1 rjung A list of further possible backports can be found at: http://people.apache.org/~rjung/patches/possible-backports-httpd-trunk-2_4.txt If you want to propose one of those, please still add them here. OTHER PROPOSALS * opinion on more complete DefaultRuntimeDir use in 2.4.x? o If a module has a config directive for the run-time file that treats the configured path as relative to server root, preserve that behavior but change the location when not configured to respect DefaultRuntimeDir. With these changes, users with no per-runtime-file configuration directives can control everything with DefaultRuntimeDir. BUT: Existing users of DefaultRuntimeDir might get a short-term scare when some unconfigured run-time file starts respecting their DefaultRuntimeDir directive after an upgrade. +1: trawick, jim, rjung rjung: applicable trunk revisions WITHOUT the compatibility tweaks described above: scoreboard r1369477 core/pid file r1369808 core/mutex r1370288 mod_socache_XXX r1370225, r1407385 mod_ldap r1371684 mod_cache r1407381 mod_slotmem_plain r1370763 igalic: We have three votes, what's the status here? Independently, backport any doc tweaks to 2.4 API migration page. PATCHES/ISSUES THAT ARE STALLED * cross-compile: allow to provide CC_FOR_BUILD so that gen_test_char will be compiled by the build compiler instead of the host compiler. Also set CC_FOR_BUILD to 'cc' when cross-compilation is detected. Trunk patches: http://svn.apache.org/viewvc?view=revision&revision=1327907 http://svn.apache.org/viewvc?view=revision&revision=1328390 http://svn.apache.org/viewvc?view=revision&revision=1328714 2.4 patch: http://people.apache.org/~fuankg/diffs/httpd-2.4.x-cross_compile.diff fuankg: on hold until we agree for a better and more simple solution ... * mod_ssl: Add support for Next Protocol Negotiation. Trunk patch: http://svn.apache.org/viewvc?view=revision&revision=1332643 2.4.x patch: Trunk patch works. +1: ben sf says: Needs r1345599, too. And wrowe's comment about the 2.2 patch is also valid for 2.4: http://svn.apache.org/viewvc?view=revision&revision=1354823 * mod_ssl: Add RFC 5878 support. This allows support of mechansisms such as Certificate Transparency. Note that new mechanisms are supported without software updates. trunk patch: http://svn.apache.org/viewvc?view=revision&revision=1352596 2.4.x patch: http://people.apache.org/~ben/httpd-2.4-rfc5878.patch +1: ben, druggeri -1: kbrand druggeri note: Needs docs for new directive kbrand: depends on an unreleased OpenSSL version (1.0.2), and RFC 5878 is of "Category: Experimental". The API in the OpenSSL implementation from May 2012 (http://cvs.openssl.org/chngview?cn=22601) only covers the privately-defined TLSEXT_AUTHZDATAFORMAT_audit_proof, there's no support for x509_attr_cert (section 3.3.1 in RFC 5878) or saml_assertion (3.3.2). SSL_CTX_use_authz_file doesn't have any docs in OpenSSL, either, and there's no "openssl foo ..." command or similar to create/manage such files. Additionally, httpd-2.4-rfc5878.patch includes a build-system change which is unrelated to this feature. Note: as of 2013-04-15, r1352596 has been reverted in trunk (with r1468131), for the reasons explained in the message with id <515FED7C.5010009@velox.ch> sent to the dev list on 2013-04-06. ben: not correct that it depends on OpenSSL 1.0.2, it builds with any version. Also, if you read my note to dev@ you will see why it is not premature. minfrin: once this gets docs, +1. * Makefile.win: Added copying of .vbs / .wsf CGIs to Windows install target. Moved fixing of shebang to separate target so that it is no longer executed by default and all CGIs remain inactive. trunk patch: http://svn.apache.org/viewvc?view=revision&revision=1387984 http://svn.apache.org/viewvc?view=revision&revision=1421203 http://svn.apache.org/viewvc?view=revision&revision=1421591 2.4.x patch: http://people.apache.org/~fuankg/diffs/httpd-2.4.x-Makefile.win.diff +1 fuankg, gsmith -.8: trawick This commit is essentially deciding that an httpd install on Windows now has printenv/testcgi written in 2 more languages. To the extent that the usefulness is that it shows how to make scripts of these types executable by httpd, I believe that the documentation is the proper place to solve that. To the extent that the usefullness is to show how to implement a CGI in these particular languages, I believe that the httpd distribution and documentation in general is not the place for that. Historically these types of scripts have caused problems for downstream vendorsas well as newbies (and sometimes the intersection of those two groups) who don't understand that these are information leaks once they are enabled, and the subtlety of the way they are disabled ("Apache messed up the first line; let me fix that") contributes to that. fuankg notes: I've just added a big warning to all CGI scripts which should now make absolutely clear that these CGIs are for testing purpose only - so those who enable those scripts with inserting the right shebang should be 100% aware of any risks (this should cover your last point). jim: trawick, does the above address your concerns? trawick: to some extent (somebody reading the script gets an idea) Why isn't the configuration requirement documented instead of described indirectly in a sample? Why are these new samples added to the install without three votes? (I didn't veto it; put your name next to the two existing ones and I'll be satisified that enough people considered this addition as an appropriate solution for a real httpd usability problem.) wrowe: I'd agree with trawick, and suggest that these scripts can begin their life somewhere in the manual/ tree. This really seems like the place where /usr/share/httpd/examples/ would be useful, but there isn't an ordinary directory for that. Since we want none of the scripts to function 'out of the box', what about a new cgi-examples/ dir alongside cgi-bin/? Otherwise manual/cgi/examples might work?