1 APACHE 2.4 STATUS: -*- mode: text; coding: utf-8 -*-
2 Last modified at [$Date$]
4 The current version of this file can be found at:
6 * http://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x/STATUS
8 Documentation status is maintained separately and can be found at:
10 * docs/STATUS in this source tree, or
11 * http://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x/docs/STATUS
13 The current development branch of this software can be found at:
15 * http://svn.apache.org/repos/asf/httpd/httpd/trunk
17 Consult the following STATUS files for information on related projects:
19 * http://svn.apache.org/repos/asf/apr/apr/trunk/STATUS
20 * http://svn.apache.org/repos/asf/apr/apr/branches/1.4.x/STATUS
21 * http://svn.apache.org/repos/asf/apr/apr-util/branches/1.4.x/STATUS
22 * http://svn.apache.org/repos/asf/apr/apr/branches/1.5.x/STATUS
23 * http://svn.apache.org/repos/asf/apr/apr-util/branches/1.5.x/STATUS
25 Patches considered for backport are noted in their branches' STATUS:
27 * http://svn.apache.org/repos/asf/httpd/httpd/branches/2.0.x/STATUS
28 * http://svn.apache.org/repos/asf/httpd/httpd/branches/2.2.x/STATUS
29 * http://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x/STATUS
34 [NOTE that x.{odd}.z versions are strictly Alpha/Beta releases,
35 while x.{even}.z versions are Stable/GA releases.]
37 2.4.19 : In development.
38 2.4.18 : Tagged on December 8, 2015. Released on December 14, 2015.
39 2.4.17 : Tagged on October 9, 2015. Released October 13, 2015.
40 2.4.16 : Tagged on July 9, 2015. Released July 15, 2015
41 2.4.15 : Tagged on June 19, 2015. Not released.
42 2.4.14 : Tagged on June 11, 2015. Not released.
43 2.4.13 : Tagged on June 4, 2015. Not released.
44 2.4.12 : Tagged on January 22, 2015. Released Jan 29, 2015
45 2.4.11 : Tagged on January 15, 2015. Not released.
46 2.4.10 : Tagged on July 15, 2014. Released July 21, 2014
47 2.4.9 : Tagged on March 13, 2014. Released on March 17, 2014
48 2.4.8 : Tagged on March 11, 2014. Not released.
49 2.4.7 : Tagged on November 19, 2013. Released on Nov 25, 2013
50 2.4.6 : Tagged on July 15, 2013. Released July, 22, 2013
51 2.4.5 : Tagged on July 11, 2013, not released.
52 2.4.4 : Tagged on February 18, 2013. Released Feb 25, 2013
53 2.4.3 : Tagged on August 17, 2012. Released Aug 18, 2012
54 2.4.2 : Tagged on April 5, 2012. Released Apr 17, 2012.
55 2.4.1 : Tagged on February 13, 2012. Released Feb 21, 2012.
56 2.4.0 : Tagged on January 16, 2012, not released.
57 2.3.16 : Tagged on December 15, 2011.
58 2.3.15 : Tagged on November 8, 2011. Released Nov. 15, 2011.
59 2.3.14 : Tagged on August 1, 2011. Released Aug. 9, 2011.
60 2.3.13 : Tagged on June 28, 2011, not released.
61 2.3.12 : Tagged on May 11, 2011. Released May 23, 2011.
62 2.3.11 : Released as Beta on March 7, 2011.
63 2.3.10 : Tagged on December 13, 2010. Released Dec 21, 2010.
64 2.3.9 : Tagged on November 23, 2010, not released.
65 2.3.8 : Tagged on August 24, 2010.
66 2.3.7 : Tagged on August 19, 2010, not released.
67 2.3.6 : Released on June 21, 2010.
68 2.3.5 : Released on January 26, 2010.
69 2.3.4 : Released on December 8, 2009.
70 2.3.3 : Tagged on November 11, 2009, not released.
71 2.3.2 : Tagged on March 23, 2009, not released.
72 2.3.1 : Tagged on January 2, 2009, not released.
73 2.3.0 : Tagged on December 6, 2008, not released.
75 Contributors looking for a mission:
77 * Just do an egrep on "TODO" or "XXX" in the source.
79 * Review the bug database at: http://issues.apache.org/bugzilla/
81 * Review the "PatchAvailable" bugs in the bug database:
83 https://issues.apache.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Apache+httpd-2&keywords=PatchAvailable
85 After testing, you can append a comment saying "Reviewed and tested".
87 * Open bugs in the bug database.
89 * See also the STATUS file in the docs/ directory, which lists documentation-specific TODO items.
92 CURRENT RELEASE NOTES:
94 * Forward binary compatibility is expected of Apache 2.4.x releases, such
95 that no MMN major number changes will occur after 2.4.1. Such changes can
96 only be made in the trunk.
98 * All commits to branches/2.4.x must be reflected in SVN trunk,
99 as well, if they apply. Logical progression is commit to trunk
100 then merge into branches/2.4.x, as applicable.
102 * Current exceptions for RTC for this branch:
107 . non-Unix, single-platform code
109 RELEASE SHOWSTOPPERS:
112 PATCHES ACCEPTED TO BACKPORT FROM TRUNK:
113 [ start all new proposals below, under PATCHES PROPOSED. ]
116 PATCHES PROPOSED TO BACKPORT FROM TRUNK:
117 [ New proposals should be added at the end of the list ]
119 *) mod_ssl: Free dhparams when getting DH params. This fixes issue when
120 SSLCryptoDevice does not get unregistered because of non-zero refcount
121 during the mod_ssl unload happening on httpd startup.
122 trunk patch: http://svn.apache.org/r1720129
123 http://svn.apache.org/r1723295
124 http://svn.apache.org/r1733088
125 http://svn.apache.org/r1733089
126 2.4.x patch: http://home.apache.org/~ylavic/patches/httpd-2.4.x-dh_leaks.patch
128 rpluem says: Can we get an updated 2.4.x proposal that includes r1723295?
129 ylavic: r1723295 + CHANGES entry now included => votes reset
131 *) mod_proxy_hcheck: Dynamic reverse proxy backend health check module
132 Trunk version of patch: <various>
133 Backport version for 2.4.x of patch:
134 http://home.apache.org/~jim/patches/hcheck-2.4-v2.patch
137 ylavic: Looks like the changes on struct proxy_worker_shared would break
138 startup with "BalancerPersist on" due to the strict checks on
139 the sizes of existing slotmems (slotmem_create/attach)?
140 jim: Yes, that is right (re: breakage)... this would be noted at
142 ylavic: OK, this is just that persisted slotmems won't be reused on first
143 startup, not that the startup will fail (as I first thought).
145 *) core: Ensure that httpd exits with an error status when the MPM fails
147 trunk patch: http://svn.apache.org/r1629925
148 http://svn.apache.org/r1629927
149 http://svn.apache.org/r1629928
150 http://svn.apache.org/r1733162
151 http://svn.apache.org/r1733173
152 2.4.x patch: http://home.apache.org/~ylavic/patches/httpd-2.4.x-exit_with_error_on_mpm_failure.patch
155 *) core/util_script: relax alphanumeric filter of enviroment variable names
156 on Windows to allow '(' and ')' for passing PROGRAMFILES(X86) et.al.
157 unadulterated in 64 bit versions of Windows. PR 46751.
158 trunk patch: http://svn.apache.org/r1705217
159 2.4.x patch: trunk patch works
161 ylavic: As asked on dev@ (in reply to r1705217), what about CVE-2014-6271
162 (shellshock) with unix-like shells (or even maybe native windows
165 *) ap_expr: expression support for variable HTTP2=on|off
166 trunk patch: http://svn.apache.org/r1726167
167 2.4.x patch: https://eissing.org/expr_http2_2.4.patch
170 *) mod_deflate: follow up to r1619444 (and to r1619383). (backported in r1669555)
171 Fix counting of inflated bytes in deflate_in_filter() when
173 trunk patch: http://svn.apache.org/r1619483
174 2.4.x patch: trunk works
177 *) mod_ssl: Add "no_crl_for_cert_ok" flag to SSLCARevocationCheck directive
178 to opt-in previous behaviour (2.2) with CRLs verification when checking
179 certificate(s) with no corresponding CRL.
180 trunk patch: http://svn.apache.org/r1734561
181 http://svn.apache.org/r1734807
182 http://svn.apache.org/r1735159
183 http://svn.apache.org/r1735337
184 2.4.x patch: trunk works (modulo CHANGES) or
185 http://home.apache.org/~ylavic/patches/httpd-2.4.x-no_crl_for_cert_ok.patch
189 PATCHES/ISSUES THAT ARE BEING WORKED
191 *) http: Don't remove the Content-Length of zero from a HEAD response if
192 it comes from an origin server, module or script. Allow the previous
193 behaviour (for legacy/buggy modules only, not origin) by also backporting
194 the HttpContentLengthHeadZero directive (and also HttpExpectStrict which
195 comes for free with the same commit).
196 trunk patch: http://svn.apache.org/r1554303
197 http://svn.apache.org/r1678215
198 2.4.x patch: http://people.apache.org/~ylavic/httpd-2.4.x-preserve_head_cl_zero.patch
200 ylavic: r1554303 issued a major MMN bump, but since the ABI change is two
201 ints added at the end of core_server_config, the proposed merge
202 does a minor bump only.
203 minfrin: Two new directives need to be documented.
205 * mod_proxy_http: Don't establish or reuse a backend connection before pre-
206 fetching the request body, so to minimize the delay between it is supposed
207 to be alive and the first bytes sent: this is a best effort to prevent the
208 backend from closing because of idle or keepalive timeout in the meantime.
209 Also, handle a new "proxy-flushall" environment variable which allows to
210 flush any forwarded body data immediately. PR 56541+37920.
211 trunk patch: http://svn.apache.org/r1656259
212 http://svn.apache.org/r1656359 (CHANGES entry)
213 2.4.x patch: trunk works (modulo CHANGES, docs/log-message-tags)
215 -0: jim: This seems to be a hit to normal performance, to handle an
216 error and/or non-normal condition. The pre-fetch is
217 expensive, and is always done, even before we know that
218 the backend is available to rec' it. I understand the
219 error described, but is the fix actually worth it (plus
220 it seems to allow for a DDoS vector).
221 ylavic: It seems to me that the problem is real since we reuse the
222 connection before prefetching 16K (either controlled by the
223 client, or by an input filter), we currently always prefetch
224 these bytes already. Regarding performance I don't see any
225 difference (more cycles) compared with the current code.
226 However I think I failed to rebuild the header_brigade when
227 the proxy loop is retried (ping), so I need to rework this.
228 Do you think we'd better remove the prefetch, or maybe just
229 make it nonblocking (by default)?
230 jim: Non-blocking seems the best way to handle...
233 PATCHES/ISSUES THAT ARE STALLED
235 * core: Add ap_errorlog_provider to make ErrorLog logging modular. This
236 backport keeps syslog logging as part of httpd core and only adds
237 API to allow other modules to be used for error logging.
238 trunk patch: http://svn.apache.org/r1525597
239 http://svn.apache.org/r1525664
240 http://svn.apache.org/r1525845
241 http://svn.apache.org/r1527003
242 http://svn.apache.org/r1527005
243 http://svn.apache.org/r1532344
244 http://svn.apache.org/r1539988
245 http://svn.apache.org/r1541029
246 http://svn.apache.org/r1543979
247 http://svn.apache.org/r1544156
248 http://svn.apache.org/r1626978
249 2.4.x patch: http://people.apache.org/~jkaluza/patches/httpd-2.4.x-errorlog_provider.patch
251 +1: covener w/ doc or code to fix syntax (providername:providerarg not supported like syslog or socacheproviders,
252 needs 2 args which is not valid in ErrorLog manual)
253 trawick: nit: fix "writing" in "/* NULL if we are writting to syslog */"
254 (sorry, haven't finished reviewing completely)
255 jim: What is the status of this??
257 * mod_proxy: Add ap_proxy_define_match_worker() and use it for ProxyPassMatch
258 and ProxyMatch section to distinguish between normal workers and workers
259 with regex substitutions in the name. Implement handling of such workers
260 in ap_proxy_get_worker(). Fixes the bug when regex workers were not
261 matched and used for request. PR 43513.
262 trunk patch: http://svn.apache.org/r1609680
263 http://svn.apache.org/r1609688
264 http://svn.apache.org/r1641381
265 ylavic: Merge patch provided (reusing new->real to avoid double de_socketfy() call).
266 Also added missing r1609688 to the patchset.
267 2.4.x patch: http://people.apache.org/~ylavic/httpd-2.4.x-ap_proxy_define_match_worker.patch
269 -0: covener tried to review this one in Austin with Jeff. Does the added match function
270 really cover a very narrow set of parameters with the way it skips over backreferences?
271 Also, why a new API vs. just setting the field inline?
273 * mod_systemd: New module, for integration with systemd on Linux.
274 trunk patch: http://svn.apache.org/r1393976
275 http://svn.apache.org/r1393997
276 http://svn.apache.org/r1484554
277 http://svn.apache.org/r1528032
278 http://svn.apache.org/r1528034
279 http://svn.apache.org/r1614821
280 http://svn.apache.org/r1618579
281 http://svn.apache.org/r1618588
282 2.4.x patch: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-mod_systemd.patch
284 sf comments: The IdleShutdown logic seems broken. Consider a single
285 active connection that is stalled for 10 seconds. That
286 connection will be broken after GracefulShutdownTimeout.
287 A better logic would be to check if there is any open
288 connection that is not in keep-alive state.
290 * mod_journald: Add new module mod_journald to log error logs into journald.
291 This patch needs changes done in mod_systemd patch (already
293 trunk patch: http://svn.apache.org/r1610339
294 http://svn.apache.org/r1621806
295 2.4.x patch: http://people.apache.org/~jkaluza/patches/httpd-2.4.x-mod_journald.patch
297 rjung, minfrin: Not understanding "This patch needs changes done in
298 mod_systemd patch", am I right in understanding this patch is
300 jkaluza: No, that patch is not committed yet. It is in STALLED section.
301 The link for that patch is: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-mod_systemd.patch
303 * core: Add support for systemd socket activation.
304 trunk patch: http://svn.apache.org/r1511033
305 http://svn.apache.org/r1608686
306 http://svn.apache.org/r1608694
307 http://svn.apache.org/r1608703
308 http://svn.apache.org/r1608721
309 http://svn.apache.org/r1608744
310 2.4.x patch: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-socket-activation.patch
313 * mod_proxy: Ensure network errors detected by the proxy are returned as
314 504 Gateway Timout as opposed to 502 Bad Gateway
315 trunk patch: https://svn.apache.org/viewvc?view=revision&revision=1480058
316 2.4.x patch: trunk patch works modulo CHANGES
318 -1: rpluem: This change is still disputed. See
319 http://mail-archives.apache.org/mod_mbox/httpd-dev/201305.mbox/%3C1B16B9E3-87BA-4EEF-939C-7C7313B54714%40gbiv.com%3E
321 * cross-compile: allow to provide CC_FOR_BUILD so that gen_test_char will be
322 compiled by the build compiler instead of the host compiler.
323 Also set CC_FOR_BUILD to 'cc' when cross-compilation is detected.
324 Trunk patches: http://svn.apache.org/viewvc?view=revision&revision=1327907
325 http://svn.apache.org/viewvc?view=revision&revision=1328390
326 http://svn.apache.org/viewvc?view=revision&revision=1328714
327 2.4 patch: http://people.apache.org/~fuankg/diffs/httpd-2.4.x-cross_compile.diff
328 fuankg: on hold until we agree for a better and more simple solution ...
330 * Makefile.win: Added copying of .vbs / .wsf CGIs to Windows install target.
331 Moved fixing of shebang to separate target so that it is
332 no longer executed by default and all CGIs remain inactive.
333 trunk patch: http://svn.apache.org/viewvc?view=revision&revision=1387984
334 http://svn.apache.org/viewvc?view=revision&revision=1421203
335 http://svn.apache.org/viewvc?view=revision&revision=1421591
336 2.4.x patch: http://people.apache.org/~fuankg/diffs/httpd-2.4.x-Makefile.win.diff
339 This commit is essentially deciding that an httpd install on
340 Windows now has printenv/testcgi written in 2 more languages.
341 To the extent that the usefulness is that it shows how to make scripts
342 of these types executable by httpd, I believe that the documentation
343 is the proper place to solve that. To the extent that the usefullness
344 is to show how to implement a CGI in these particular languages, I believe
345 that the httpd distribution and documentation in general is not the
346 place for that. Historically these types of scripts have caused problems
347 for downstream vendorsas well as newbies (and sometimes the intersection
348 of those two groups) who don't understand that these are information leaks
349 once they are enabled, and the subtlety of the way they are disabled ("Apache
350 messed up the first line; let me fix that") contributes to that.
351 fuankg notes: I've just added a big warning to all CGI scripts which should now
352 make absolutely clear that these CGIs are for testing purpose only - so those
353 who enable those scripts with inserting the right shebang should be 100% aware
354 of any risks (this should cover your last point).
355 jim: trawick, does the above address your concerns?
356 trawick: to some extent (somebody reading the script gets an idea)
357 Why isn't the configuration requirement documented instead
358 of described indirectly in a sample?
359 Why are these new samples added to the install without three
360 votes? (I didn't veto it; put your name next to the two
361 existing ones and I'll be satisified that enough people
362 considered this addition as an appropriate solution for a
363 real httpd usability problem.)
364 wrowe: I'd agree with trawick, and suggest that these scripts can begin
365 their life somewhere in the manual/ tree. This really seems like
366 the place where /usr/share/httpd/examples/ would be useful, but
367 there isn't an ordinary directory for that. Since we want none
368 of the scripts to function 'out of the box', what about a new
369 cgi-examples/ dir alongside cgi-bin/? Otherwise manual/cgi/examples