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.26 : In development.
38 2.4.25 : Tagged on December 16, 2016. Released on December 21, 2016.
39 2.4.24 : Tagged on December 16, 2016, not released.
40 2.4.23 : Tagged on June 30, 2016. Released on July 05, 2016.
41 2.4.22 : Tagged on June 20, 2016, not released.
42 2.4.21 : Tagged on June 16, 2016, not released.
43 2.4.20 : Tagged on April 4, 2016. Released on April 11, 2016.
44 2.4.19 : Tagged on March 21, 2016, not released.
45 2.4.18 : Tagged on December 8, 2015. Released on December 14, 2015.
46 2.4.17 : Tagged on October 9, 2015. Released October 13, 2015.
47 2.4.16 : Tagged on July 9, 2015. Released July 15, 2015
48 2.4.15 : Tagged on June 19, 2015. Not released.
49 2.4.14 : Tagged on June 11, 2015. Not released.
50 2.4.13 : Tagged on June 4, 2015. Not released.
51 2.4.12 : Tagged on January 22, 2015. Released Jan 29, 2015
52 2.4.11 : Tagged on January 15, 2015. Not released.
53 2.4.10 : Tagged on July 15, 2014. Released July 21, 2014
54 2.4.9 : Tagged on March 13, 2014. Released on March 17, 2014
55 2.4.8 : Tagged on March 11, 2014. Not released.
56 2.4.7 : Tagged on November 19, 2013. Released on Nov 25, 2013
57 2.4.6 : Tagged on July 15, 2013. Released July, 22, 2013
58 2.4.5 : Tagged on July 11, 2013, not released.
59 2.4.4 : Tagged on February 18, 2013. Released Feb 25, 2013
60 2.4.3 : Tagged on August 17, 2012. Released Aug 18, 2012
61 2.4.2 : Tagged on April 5, 2012. Released Apr 17, 2012.
62 2.4.1 : Tagged on February 13, 2012. Released Feb 21, 2012.
63 2.4.0 : Tagged on January 16, 2012, not released.
64 2.3.16 : Tagged on December 15, 2011.
65 2.3.15 : Tagged on November 8, 2011. Released Nov. 15, 2011.
66 2.3.14 : Tagged on August 1, 2011. Released Aug. 9, 2011.
67 2.3.13 : Tagged on June 28, 2011, not released.
68 2.3.12 : Tagged on May 11, 2011. Released May 23, 2011.
69 2.3.11 : Released as Beta on March 7, 2011.
70 2.3.10 : Tagged on December 13, 2010. Released Dec 21, 2010.
71 2.3.9 : Tagged on November 23, 2010, not released.
72 2.3.8 : Tagged on August 24, 2010.
73 2.3.7 : Tagged on August 19, 2010, not released.
74 2.3.6 : Released on June 21, 2010.
75 2.3.5 : Released on January 26, 2010.
76 2.3.4 : Released on December 8, 2009.
77 2.3.3 : Tagged on November 11, 2009, not released.
78 2.3.2 : Tagged on March 23, 2009, not released.
79 2.3.1 : Tagged on January 2, 2009, not released.
80 2.3.0 : Tagged on December 6, 2008, not released.
82 Contributors looking for a mission:
84 * Just do an egrep on "TODO" or "XXX" in the source.
86 * Review the bug database at: http://issues.apache.org/bugzilla/
88 * Review the "PatchAvailable" bugs in the bug database:
90 https://issues.apache.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Apache+httpd-2&keywords=PatchAvailable
92 After testing, you can append a comment saying "Reviewed and tested".
94 * Open bugs in the bug database.
96 * See also the STATUS file in the docs/ directory, which lists documentation-specific TODO items.
99 CURRENT RELEASE NOTES:
101 * Forward binary compatibility is expected of Apache 2.4.x releases, such
102 that no MMN major number changes will occur after 2.4.1. Such changes can
103 only be made in the trunk.
105 * All commits to branches/2.4.x must be reflected in SVN trunk,
106 as well, if they apply. Logical progression is commit to trunk
107 then merge into branches/2.4.x, as applicable.
109 * Current exceptions for RTC for this branch:
114 . non-Unix, single-platform code
116 RELEASE SHOWSTOPPERS:
118 *) PR 60071: Child httpd processes crash with Segmentation fault
119 trunk patch: http://svn.apache.org/r1779573
120 http://svn.apache.org/r1779574
121 http://svn.apache.org/r1779623
122 2.4.x patch: trunk works
125 *) PR60458: Rip out this regression or fix (TBD)
127 PATCHES ACCEPTED TO BACKPORT FROM TRUNK:
128 [ start all new proposals below, under PATCHES PROPOSED. ]
132 PATCHES PROPOSED TO BACKPORT FROM TRUNK:
133 [ New proposals should be added at the end of the list ]
135 *) mod_proxy, mod_ssl: Handle SSLProxy* directives in <Proxy> sections,
136 allowing per backend TLS configuration.
137 trunk patch: http://svn.apache.org/r1740928
138 http://svn.apache.org/r1740960
139 http://svn.apache.org/r1740967
140 http://svn.apache.org/r1740987
141 http://svn.apache.org/r1740998
142 http://svn.apache.org/r1742697
143 http://svn.apache.org/r1756976
144 http://svn.apache.org/r1781313
145 2.4.x patch: http://home.apache.org/~ylavic/patches/httpd-2.4.x-r1740928_and_co-v3.patch
148 *) event: close a race condition where we might re-enable listeners while they
149 are already or about to be closed.
150 trunk patch: http://svn.apache.org/r1774541
151 2.4.x patch: trunk works
154 *) mod_proxy_fcgi: Return HTTP 504 rather than 503 in case of proxy timeout.
155 trunk patch: http://svn.apache.org/r1775858
156 2.4 patch: trunk works (modulo CHANGES)
159 *) mod_remoteip: Add PROXY protocol support
160 trunk patch: http://svn.apache.org/r1776575
161 http://svn.apache.org/r1776578 (doc fix)
162 http://svn.apache.org/r1776627 (shortened name + doc fix)
163 http://svn.apache.org/r1776674 (attribution moved to CHANGES)
164 http://svn.apache.org/r1776740 (attribution updated in mod_remotip.c)
165 http://svn.apache.org/r1778268 (fix compiler warning)
166 http://svn.apache.org/r1780725 (set buckets aside)
167 http://svn.apache.org/r1781030 (fix strict GCC warning)
168 http://svn.apache.org/r1781031 (reference the filter by handle)
169 http://svn.apache.org/r1781701 (rework optional processing case)
170 2.4 convenience patch (includes CHANGES):
171 http://people.apache.org/~druggeri/patches/RemoteIPProxyProtocol.2.4.x.patch
174 *) mod_brotli: Backport of mod_brotli filter
175 trunk patch: http://svn.apache.org/r1761714
176 http://svn.apache.org/r1762512
177 http://svn.apache.org/r1762515
178 http://svn.apache.org/r1771791
179 http://svn.apache.org/r1779077
180 2.4.x patch: http://home.apache.org/~jim/patches/brotli-2.4.patch
182 jailletc36: doc should also be back-ported (r1779091 + r1779699)
184 *) mod_ssl: work around leaks on (graceful) restart.
185 trunk patch: http://svn.apache.org/r1781187
186 http://svn.apache.org/r1781190
187 http://svn.apache.org/r1781312
188 2.4.x patch: http://home.apache.org/~ylavic/patches/httpd-2.4.x-mod_ssl-restart_leaks-v2.patch
191 *) mod_proxy_hcheck: Ensure thread-safety when concurrent healthchecks are
192 in use (ProxyHCTPsize > 0). PR 60071.
193 trunk patch: http://svn.apache.org/r1779573
194 2.4.x patch: trunk works (modulo CHANGES)
197 *) mod_proxy_hcheck: Don't validate timed out responses.
198 trunk patch: http://svn.apache.org/r1779574
199 http://svn.apache.org/r1779623
200 2.4.x patch: trunk works *after r1779573 above* (modulo CHANGES)
203 *) PR 60576: 2.4.21 broke PHP-FPM with the patch to strip the bogus "proxy://"
204 prefix from SCRIPT_FILENAME. We need to revert to the previous behavior
205 ASAP to avoid any further hurdles with FCGI implementations while we figure
207 trunk patch: http://svn.apache.org/r1780328
208 http://svn.apache.org/r1780329
209 http://svn.apache.org/r1781329
210 http://svn.apache.org/r1782164
211 http://svn.apache.org/r1782166
212 http://svn.apache.org/r1782193
213 http://svn.apache.org/r1778350
214 http://svn.apache.org/r1781329
215 http://svn.apache.org/r1782194
216 http://svn.apache.org/r1782323
217 2.4.x patch: http://home.apache.org/~jim/patches/mod_proxy_fcgi-v2.patch
221 PATCHES/ISSUES THAT ARE BEING WORKED
222 [ New entried should be added at the START of the list ]
224 *) mod_ssl: Return 502 instead of 500 when SSL peer check or
225 proxy_post_handshake hook fails.
226 Trunk patch: r1645529 (works)
227 2.4.x patch which adds CHANGES: https://emptyhammock.com/media/downloads/r1645529-to-2.4.x.txt
229 ylavic: there may be missing bits, see thread for commit r1736510.
231 *) core: Drop an invalid Last-Modified header value coming
232 from a (F)CGI script instead of replacing it with Unix epoch.
233 Warn the users about Last-Modified header value replacements
234 and violations of the RFC.
235 trunk patch: http://svn.apache.org/r1748379
236 http://svn.apache.org/r1750747
237 http://svn.apache.org/r1750749
238 http://svn.apache.org/r1750953
239 http://svn.apache.org/r1751138
240 http://svn.apache.org/r1751139
241 http://svn.apache.org/r1751147
242 http://svn.apache.org/r1757818
243 2.4.x: trunk patches work, final view:
244 http://home.apache.org/~elukey/httpd-2.4.x-core-last_modified_tz_logging.patch
245 The problem has been discussed in dev@ extensively but we did not reach a common
246 agreement about how to proceed in the long term. While we wait, I would really like
247 to introduce useful logs for the users (the starting point of this change was a users@
248 email thread). If this is not the right way to go I will move the patch to other
249 sections of STATUS (stalled or being worked).
250 The code has been tested with a simple PHP script returning different Last-Modified
251 headers (GMT now, GMT now Europe/Paris, GMT tomorrow, GMT yesterday, PST now).
254 *) http: Don't remove the Content-Length of zero from a HEAD response if
255 it comes from an origin server, module or script. Allow the previous
256 behaviour (for legacy/buggy modules only, not origin) by also backporting
257 the HttpContentLengthHeadZero directive (and also HttpExpectStrict which
258 comes for free with the same commit).
259 trunk patch: http://svn.apache.org/r1554303
260 http://svn.apache.org/r1678215
261 2.4.x patch: http://people.apache.org/~ylavic/httpd-2.4.x-preserve_head_cl_zero.patch
263 ylavic: r1554303 issued a major MMN bump, but since the ABI change is two
264 ints added at the end of core_server_config, the proposed merge
265 does a minor bump only.
266 minfrin: Two new directives need to be documented.
268 * mod_proxy_http: Don't establish or reuse a backend connection before pre-
269 fetching the request body, so to minimize the delay between it is supposed
270 to be alive and the first bytes sent: this is a best effort to prevent the
271 backend from closing because of idle or keepalive timeout in the meantime.
272 Also, handle a new "proxy-flushall" environment variable which allows to
273 flush any forwarded body data immediately. PR 56541+37920.
274 trunk patch: http://svn.apache.org/r1656259
275 http://svn.apache.org/r1656359 (CHANGES entry)
276 2.4.x patch: trunk works (modulo CHANGES, docs/log-message-tags)
278 -0: jim: This seems to be a hit to normal performance, to handle an
279 error and/or non-normal condition. The pre-fetch is
280 expensive, and is always done, even before we know that
281 the backend is available to rec' it. I understand the
282 error described, but is the fix actually worth it (plus
283 it seems to allow for a DDoS vector).
284 ylavic: It seems to me that the problem is real since we reuse the
285 connection before prefetching 16K (either controlled by the
286 client, or by an input filter), we currently always prefetch
287 these bytes already. Regarding performance I don't see any
288 difference (more cycles) compared with the current code.
289 However I think I failed to rebuild the header_brigade when
290 the proxy loop is retried (ping), so I need to rework this.
291 Do you think we'd better remove the prefetch, or maybe just
292 make it nonblocking (by default)?
293 jim: Non-blocking seems the best way to handle...
295 * mod_dav: Allow other modules to become providers and add ACLs
296 to the DAV response. Requires a release of apr-util v1.6.
297 trunk patch: http://svn.apache.org/r1748322
298 2.4.x: trunk works modulo CHANGES/MMN
300 rpluem asks: Will this compile with apr-util < v1.6 and keep
301 mod_dav working (without the new features of the patch of course)?
302 I doubt that we will require apr-util 1.6 for the lifetime of 2.4.x
303 (see the discussion around ap_cstr_casecmp[n] an apr 1.6)
304 minfrin: Yes, as you can see in the patch everything applies only
305 if APR_XML_X2T_PARSED is defined, and the patch was tested with
306 both apr-util v1.6 and apr-util v1.5.
307 -1: jorton, breaks binary backwards compat per dev@ discuss
308 msgid <20160902120654.GA12674@redhat.com>
309 (& also, making the structure change with apr-util version
310 means it breaks binary compat across an apr-util upgrade?)
312 * Support PCRE2 (10.x) in place of PCRE (8.x).
313 Submitted by: wrowe, Petr Pisar [ppisar redhat.com]
315 http://svn.apache.org/r1773454
316 http://svn.apache.org/r1773741
317 http://svn.apache.org/r1773742
318 http://svn.apache.org/r1773839
319 http://svn.apache.org/r1773870
320 http://svn.apache.org/r1773882
321 wrowe notes that the current code is too inefficient, owing to the fact
322 that the ovector is a required allocation and is no longer allocated on
323 the stack, by design. The correct fix is an apr userdata allocation on
324 the appropriate pool, which would be thread-safe, but the actual API of
325 ap_regexec[_len]() offers us no pool. We cannot associate that pool with
326 the ap_regex_t, because a single regex may be used by many threads in
327 parallel and is not thread-safe beyond initialization.
328 So the only fix allowing us to use PCRE 10 in httpd 2.4 would be to write
329 this as a thread safe storage buffer for the majority of cases (<10 $args)
330 and we don't have a portable tls mechanism to do so.
333 PATCHES/ISSUES THAT ARE STALLED
335 * core: Add ap_errorlog_provider to make ErrorLog logging modular. This
336 backport keeps syslog logging as part of httpd core and only adds
337 API to allow other modules to be used for error logging.
338 trunk patch: http://svn.apache.org/r1525597
339 http://svn.apache.org/r1525664
340 http://svn.apache.org/r1525845
341 http://svn.apache.org/r1527003
342 http://svn.apache.org/r1527005
343 http://svn.apache.org/r1532344
344 http://svn.apache.org/r1539988
345 http://svn.apache.org/r1541029
346 http://svn.apache.org/r1543979
347 http://svn.apache.org/r1544156
348 http://svn.apache.org/r1626978
349 2.4.x patch: http://people.apache.org/~jkaluza/patches/httpd-2.4.x-errorlog_provider.patch
351 +1: covener w/ doc or code to fix syntax (providername:providerarg not supported like syslog or socacheproviders,
352 needs 2 args which is not valid in ErrorLog manual)
353 trawick: nit: fix "writing" in "/* NULL if we are writing to syslog */"
354 (sorry, haven't finished reviewing completely)
355 jim: What is the status of this??
357 * mod_proxy: Add ap_proxy_define_match_worker() and use it for ProxyPassMatch
358 and ProxyMatch section to distinguish between normal workers and workers
359 with regex substitutions in the name. Implement handling of such workers
360 in ap_proxy_get_worker(). Fixes the bug when regex workers were not
361 matched and used for request. PR 43513.
362 trunk patch: http://svn.apache.org/r1609680
363 http://svn.apache.org/r1609688
364 http://svn.apache.org/r1641381
365 ylavic: Merge patch provided (reusing new->real to avoid double de_socketfy() call).
366 Also added missing r1609688 to the patchset.
367 2.4.x patch: http://people.apache.org/~ylavic/httpd-2.4.x-ap_proxy_define_match_worker.patch
369 -0: covener tried to review this one in Austin with Jeff. Does the added match function
370 really cover a very narrow set of parameters with the way it skips over backreferences?
371 Also, why a new API vs. just setting the field inline?
373 * mod_systemd: New module, for integration with systemd on Linux.
374 trunk patch: http://svn.apache.org/r1393976
375 http://svn.apache.org/r1393997
376 http://svn.apache.org/r1484554
377 http://svn.apache.org/r1528032
378 http://svn.apache.org/r1528034
379 http://svn.apache.org/r1614821
380 http://svn.apache.org/r1618579
381 http://svn.apache.org/r1618588
382 2.4.x patch: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-mod_systemd.patch
384 sf comments: The IdleShutdown logic seems broken. Consider a single
385 active connection that is stalled for 10 seconds. That
386 connection will be broken after GracefulShutdownTimeout.
387 A better logic would be to check if there is any open
388 connection that is not in keep-alive state.
390 * mod_journald: Add new module mod_journald to log error logs into journald.
391 This patch needs changes done in mod_systemd patch (already
393 trunk patch: http://svn.apache.org/r1610339
394 http://svn.apache.org/r1621806
395 2.4.x patch: http://people.apache.org/~jkaluza/patches/httpd-2.4.x-mod_journald.patch
397 rjung, minfrin: Not understanding "This patch needs changes done in
398 mod_systemd patch", am I right in understanding this patch is
400 jkaluza: No, that patch is not committed yet. It is in STALLED section.
401 The link for that patch is: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-mod_systemd.patch
403 * core: Add support for systemd socket activation.
404 trunk patch: http://svn.apache.org/r1511033
405 http://svn.apache.org/r1608686
406 http://svn.apache.org/r1608694
407 http://svn.apache.org/r1608703
408 http://svn.apache.org/r1608721
409 http://svn.apache.org/r1608744
410 2.4.x patch: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-socket-activation.patch
413 * mod_proxy: Ensure network errors detected by the proxy are returned as
414 504 Gateway Timeout as opposed to 502 Bad Gateway
415 trunk patch: https://svn.apache.org/viewvc?view=revision&revision=1480058
416 2.4.x patch: trunk patch works modulo CHANGES
418 -1: rpluem: This change is still disputed. See
419 http://mail-archives.apache.org/mod_mbox/httpd-dev/201305.mbox/%3C1B16B9E3-87BA-4EEF-939C-7C7313B54714%40gbiv.com%3E
421 * cross-compile: allow to provide CC_FOR_BUILD so that gen_test_char will be
422 compiled by the build compiler instead of the host compiler.
423 Also set CC_FOR_BUILD to 'cc' when cross-compilation is detected.
424 Trunk patches: http://svn.apache.org/viewvc?view=revision&revision=1327907
425 http://svn.apache.org/viewvc?view=revision&revision=1328390
426 http://svn.apache.org/viewvc?view=revision&revision=1328714
427 2.4 patch: http://people.apache.org/~fuankg/diffs/httpd-2.4.x-cross_compile.diff
428 fuankg: on hold until we agree for a better and more simple solution ...
430 * Makefile.win: Added copying of .vbs / .wsf CGIs to Windows install target.
431 Moved fixing of shebang to separate target so that it is
432 no longer executed by default and all CGIs remain inactive.
433 trunk patch: http://svn.apache.org/viewvc?view=revision&revision=1387984
434 http://svn.apache.org/viewvc?view=revision&revision=1421203
435 http://svn.apache.org/viewvc?view=revision&revision=1421591
436 2.4.x patch: http://people.apache.org/~fuankg/diffs/httpd-2.4.x-Makefile.win.diff
439 This commit is essentially deciding that an httpd install on
440 Windows now has printenv/testcgi written in 2 more languages.
441 To the extent that the usefulness is that it shows how to make scripts
442 of these types executable by httpd, I believe that the documentation
443 is the proper place to solve that. To the extent that the usefullness
444 is to show how to implement a CGI in these particular languages, I believe
445 that the httpd distribution and documentation in general is not the
446 place for that. Historically these types of scripts have caused problems
447 for downstream vendorsas well as newbies (and sometimes the intersection
448 of those two groups) who don't understand that these are information leaks
449 once they are enabled, and the subtlety of the way they are disabled ("Apache
450 messed up the first line; let me fix that") contributes to that.
451 fuankg notes: I've just added a big warning to all CGI scripts which should now
452 make absolutely clear that these CGIs are for testing purpose only - so those
453 who enable those scripts with inserting the right shebang should be 100% aware
454 of any risks (this should cover your last point).
455 jim: trawick, does the above address your concerns?
456 trawick: to some extent (somebody reading the script gets an idea)
457 Why isn't the configuration requirement documented instead
458 of described indirectly in a sample?
459 Why are these new samples added to the install without three
460 votes? (I didn't veto it; put your name next to the two
461 existing ones and I'll be satisfied that enough people
462 considered this addition as an appropriate solution for a
463 real httpd usability problem.)
464 wrowe: I'd agree with trawick, and suggest that these scripts can begin
465 their life somewhere in the manual/ tree. This really seems like
466 the place where /usr/share/httpd/examples/ would be useful, but
467 there isn't an ordinary directory for that. Since we want none
468 of the scripts to function 'out of the box', what about a new
469 cgi-examples/ dir alongside cgi-bin/? Otherwise manual/cgi/examples
472 * core: block Define and Undefine in vhost and directory context. Because
473 it is EXEC_ON_READ, it "breaks out" of these contexts anyway.
474 trunk patch: http://svn.apache.org/r1656063
475 http://svn.apache.org/r1656122
476 2.4.x patch: http://people.apache.org/~covener/patches/2.4.x-define-limits.diff
477 +1: covener (I need to review the docs manually in this area)
478 -1: wrowe (blocking will break "working" .conf files on a subversion update
479 meant to pick up security fixes. "Alerting" I would agree to.)