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 The current development branch of this software can be found at:
10 * http://svn.apache.org/repos/asf/httpd/httpd/trunk
12 Consult the following STATUS files for information on related projects:
14 * http://svn.apache.org/repos/asf/apr/apr/trunk/STATUS
15 * http://svn.apache.org/repos/asf/apr/apr/branches/1.4.x/STATUS
16 * http://svn.apache.org/repos/asf/apr/apr-util/branches/1.4.x/STATUS
17 * http://svn.apache.org/repos/asf/apr/apr/branches/1.5.x/STATUS
18 * http://svn.apache.org/repos/asf/apr/apr-util/branches/1.5.x/STATUS
19 * http://svn.apache.org/repos/asf/apr/apr/branches/1.6.x/STATUS
20 * http://svn.apache.org/repos/asf/apr/apr-util/branches/1.6.x/STATUS
22 Patches considered for backport are noted in their branches' STATUS:
24 * http://svn.apache.org/repos/asf/httpd/httpd/branches/2.2.x/STATUS
25 * http://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x/STATUS
29 [NOTE that x.{odd}.z versions are strictly Alpha/Beta releases,
30 while x.{even}.z versions are Stable/GA releases.]
32 2.4.29 : In development.
33 2.4.28 : Tagged on September 25, 2017. Released on October 5, 2017.
34 2.4.27 : Tagged on July 6, 2017. Released on July 11, 2017.
35 2.4.26 : Tagged on June 13, 2017. Released on June 19, 2017.
36 2.4.25 : Tagged on December 16, 2016. Released on December 21, 2016.
37 2.4.24 : Tagged on December 16, 2016, not released.
38 2.4.23 : Tagged on June 30, 2016. Released on July 05, 2016.
39 2.4.22 : Tagged on June 20, 2016, not released.
40 2.4.21 : Tagged on June 16, 2016, not released.
41 2.4.20 : Tagged on April 4, 2016. Released on April 11, 2016.
42 2.4.19 : Tagged on March 21, 2016, not released.
43 2.4.18 : Tagged on December 8, 2015. Released on December 14, 2015.
44 2.4.17 : Tagged on October 9, 2015. Released October 13, 2015.
45 2.4.16 : Tagged on July 9, 2015. Released July 15, 2015
46 2.4.15 : Tagged on June 19, 2015. Not released.
47 2.4.14 : Tagged on June 11, 2015. Not released.
48 2.4.13 : Tagged on June 4, 2015. Not released.
49 2.4.12 : Tagged on January 22, 2015. Released Jan 29, 2015
50 2.4.11 : Tagged on January 15, 2015. Not released.
51 2.4.10 : Tagged on July 15, 2014. Released July 21, 2014
52 2.4.9 : Tagged on March 13, 2014. Released on March 17, 2014
53 2.4.8 : Tagged on March 11, 2014. Not released.
54 2.4.7 : Tagged on November 19, 2013. Released on Nov 25, 2013
55 2.4.6 : Tagged on July 15, 2013. Released July, 22, 2013
56 2.4.5 : Tagged on July 11, 2013, not released.
57 2.4.4 : Tagged on February 18, 2013. Released Feb 25, 2013
58 2.4.3 : Tagged on August 17, 2012. Released Aug 18, 2012
59 2.4.2 : Tagged on April 5, 2012. Released Apr 17, 2012.
60 2.4.1 : Tagged on February 13, 2012. Released Feb 21, 2012.
61 2.4.0 : Tagged on January 16, 2012, not released.
62 2.3.16 : Tagged on December 15, 2011.
63 2.3.15 : Tagged on November 8, 2011. Released Nov. 15, 2011.
64 2.3.14 : Tagged on August 1, 2011. Released Aug. 9, 2011.
65 2.3.13 : Tagged on June 28, 2011, not released.
66 2.3.12 : Tagged on May 11, 2011. Released May 23, 2011.
67 2.3.11 : Released as Beta on March 7, 2011.
68 2.3.10 : Tagged on December 13, 2010. Released Dec 21, 2010.
69 2.3.9 : Tagged on November 23, 2010, not released.
70 2.3.8 : Tagged on August 24, 2010.
71 2.3.7 : Tagged on August 19, 2010, not released.
72 2.3.6 : Released on June 21, 2010.
73 2.3.5 : Released on January 26, 2010.
74 2.3.4 : Released on December 8, 2009.
75 2.3.3 : Tagged on November 11, 2009, not released.
76 2.3.2 : Tagged on March 23, 2009, not released.
77 2.3.1 : Tagged on January 2, 2009, not released.
78 2.3.0 : Tagged on December 6, 2008, not released.
80 Contributors looking for a mission:
82 * Just do an egrep on "TODO" or "XXX" in the source.
84 * Review the bug database at: http://issues.apache.org/bugzilla/
86 * Review the "PatchAvailable" bugs in the bug database:
88 https://issues.apache.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Apache+httpd-2&keywords=PatchAvailable
90 After testing, you can append a comment saying "Reviewed and tested".
92 * Open bugs in the bug database.
94 * See also the STATUS file in the docs/ directory, which lists documentation-specific TODO items.
97 CURRENT RELEASE NOTES:
99 * Forward binary compatibility is expected of Apache 2.4.x releases, such
100 that no MMN major number changes will occur after 2.4.1. Such changes can
101 only be made in the trunk.
103 * All commits to branches/2.4.x must be reflected in SVN trunk,
104 as well, if they apply. Logical progression is commit to trunk
105 then merge into branches/2.4.x, as applicable.
107 * Current exceptions for RTC for this branch:
112 . non-Unix, single-platform code
114 RELEASE SHOWSTOPPERS:
117 PATCHES ACCEPTED TO BACKPORT FROM TRUNK:
118 [ start all new proposals below, under PATCHES PROPOSED. ]
122 PATCHES PROPOSED TO BACKPORT FROM TRUNK:
123 [ New proposals should be added at the end of the list ]
125 *) mod_proxy, mod_ssl: Handle SSLProxy* directives in <Proxy> sections,
126 allowing per backend TLS configuration.
127 trunk patch: http://svn.apache.org/r1740928
128 http://svn.apache.org/r1740960
129 http://svn.apache.org/r1740967
130 http://svn.apache.org/r1740987
131 http://svn.apache.org/r1740998
132 http://svn.apache.org/r1742697
133 http://svn.apache.org/r1756976
134 http://svn.apache.org/r1781313
135 2.4.x patch: http://home.apache.org/~ylavic/patches/httpd-2.4.x-r1740928_and_co-v3.patch
137 mrumph: Since this has been sitting for awhile, there are several places
138 where this patch needs to be adjusted against recent changes to 2.4.x.
139 ylavic: With current 2.4.x (r1807662), there seems to be only a conflict with
140 MMN, which can probably be taken by the backporter. I don't see the
141 other places where it needs adjustments, Mike?
142 wrowe: Suspect that this is an MMN Major bump, not minor, without some
143 additional detection/workaround of legacy 2.4 compiled modules.
145 *) mod_remoteip: Add PROXY protocol support
146 trunk patch: http://svn.apache.org/r1776575
147 http://svn.apache.org/r1776578 (doc fix)
148 http://svn.apache.org/r1776627 (shortened name + doc fix)
149 http://svn.apache.org/r1776674 (attribution moved to CHANGES)
150 http://svn.apache.org/r1776740 (attribution updated in mod_remotip.c)
151 http://svn.apache.org/r1778268 (fix compiler warning)
152 http://svn.apache.org/r1780725 (set buckets aside)
153 http://svn.apache.org/r1781030 (fix strict GCC warning)
154 http://svn.apache.org/r1781031 (reference the filter by handle)
155 http://svn.apache.org/r1781701 (rework optional processing case)
156 http://svn.apache.org/r1788674 (final edge cases/ignore slave conns)
157 http://svn.apache.org/r1789800 (remove optional processing)
158 http://svn.apache.org/r1790169 (rename "exception" directive)
159 http://svn.apache.org/r1790457 (Update directive name in err message)
160 http://svn.apache.org/r1806985
161 2.4 convenience patch (includes CHANGES):
162 http://home.apache.org/~jim/patches/RemoteIPProxyProtocol.2.4.x.patch
163 http://svn.apache.org/r1806985
165 mrumph: I had a chance to review this proposal.
166 I committed some suggested changes to trunk in r1806985.
167 Also, the copyright in mod_remoteip.c is of some concern.
168 Perhaps the terms of the copyright should be included in that note.
169 And on a personal note, today is my last day with Oracle.
170 So it may well be my last day with Apache as well.
171 It has been great working with all of you.
172 jim: Not sure what the copyright concern is, but added r1806985
174 ylavic: RemoteIPProxyProtocol* are documented as scoped to server config
175 and virtual host, though using ap_server_conf makes them global
176 only (thus less useful too...).
178 *) mod_journald: Add new module mod_journald to log error logs into journald.
179 trunk patch: http://svn.apache.org/r1610339
180 http://svn.apache.org/r1621806
181 2.4.x patch: http://people.apache.org/~jkaluza/patches/httpd-2.4.x-mod_journald.patch
183 jchampion: Looks like the headers require GCC extensions to compile, so
184 mod_journald can't be configured in maintainer mode (-std=c89).
185 Can anyone else reproduce, or is it just my distro?
187 *) core/mod_ssl: Add new flag int to module struct. Define first bit for keeping
188 server config records non-shared instances, set for mod_ssl to make manipulations
190 trunk patch: svn merge -c 1809302,1809303,1809305,1809311,1809314,1809713 ^/httpd/httpd/trunk .
191 2.4.x patch: https://svn.apache.org/repos/asf/httpd/httpd/patches/2.4.x/backport-module-flags.diff
192 (merge with alterations for mmn etc.)
195 *) core: A signal received while stopping could have crashed the main
197 trunk patch: http://svn.apache.org/r1809881
198 http://svn.apache.org/r1809973
199 http://svn.apache.org/r1809976
200 http://svn.apache.org/r1812075
201 2.4.x patch: https://svn.apache.org/repos/asf/httpd/httpd/patches/2.4.x/stop_signals-PR61558.patch
202 (merge without changes to motorz)
205 *) configure.in: Latest macOS Xcode 9 installs clang-900, which more
206 fully honors strict-prototypes, which causes AC_CHECK_LIB to
207 fail when --enable-maintainer-mode is set. Also affects clang 5.
208 trunk patch: http://svn.apache.org/r1810448
209 http://svn.apache.org/r1810998
210 2.4.x patch: svn merge -c 1810448,1810998 ^/httpd/httpd/trunk .
213 [This seems to fit into the mold of per-platform quirks which we process
214 in CTR flow, adding my +1 to note that the patch looks sane.]
215 rjung: I think we need this also for GCC, not only recent clang.
216 See my below suggestion (r1812263)
218 *) configure.in: Fix maintainer mode with GCC/Clang.
219 Setting -Wstrict-prototypes in combination with -Werror leads to compiler
220 errors during configure checks (autoconf generates incomplete prototypes).
221 Adding -Wno-error=strict-prototypes lets the compiler tolerate those.
222 Possible future enhancement: remember such "configure time only" flags and
223 remove them from CFLAGS before generating our build time files
224 (Makefile, config_vars.mk etc.), so that the full -Werror is in place
226 trunk patch: http://svn.apache.org/r1812263
227 2.4.x patch: svn merge -c r1812263 ^/httpd/httpd/trunk .
231 PATCHES/ISSUES THAT ARE BEING WORKED
232 [ New entries should be added at the START of the list ]
234 *) mod_ssl: Return 502 instead of 500 when SSL peer check or
235 proxy_post_handshake hook fails.
236 Trunk patch: r1645529 (works)
237 2.4.x patch which adds CHANGES: https://emptyhammock.com/media/downloads/r1645529-to-2.4.x.txt
239 ylavic: there may be missing bits, see thread for commit r1736510.
241 *) core: Drop an invalid Last-Modified header value coming
242 from a (F)CGI script instead of replacing it with Unix epoch.
243 Warn the users about Last-Modified header value replacements
244 and violations of the RFC.
245 trunk patch: http://svn.apache.org/r1748379
246 http://svn.apache.org/r1750747
247 http://svn.apache.org/r1750749
248 http://svn.apache.org/r1750953
249 http://svn.apache.org/r1751138
250 http://svn.apache.org/r1751139
251 http://svn.apache.org/r1751147
252 http://svn.apache.org/r1757818
253 2.4.x: trunk patches work, final view:
254 http://home.apache.org/~elukey/httpd-2.4.x-core-last_modified_tz_logging.patch
255 The problem has been discussed in dev@ extensively but we did not reach a common
256 agreement about how to proceed in the long term. While we wait, I would really like
257 to introduce useful logs for the users (the starting point of this change was a users@
258 email thread). If this is not the right way to go I will move the patch to other
259 sections of STATUS (stalled or being worked).
260 The code has been tested with a simple PHP script returning different Last-Modified
261 headers (GMT now, GMT now Europe/Paris, GMT tomorrow, GMT yesterday, PST now).
264 *) http: Don't remove the Content-Length of zero from a HEAD response if
265 it comes from an origin server, module or script. Allow the previous
266 behaviour (for legacy/buggy modules only, not origin) by also backporting
267 the HttpContentLengthHeadZero directive (and also HttpExpectStrict which
268 comes for free with the same commit).
269 trunk patch: http://svn.apache.org/r1554303
270 http://svn.apache.org/r1678215
271 2.4.x patch: http://people.apache.org/~ylavic/httpd-2.4.x-preserve_head_cl_zero.patch
273 ylavic: r1554303 issued a major MMN bump, but since the ABI change is two
274 ints added at the end of core_server_config, the proposed merge
275 does a minor bump only.
276 minfrin: Two new directives need to be documented.
278 * mod_proxy_http: Don't establish or reuse a backend connection before pre-
279 fetching the request body, so to minimize the delay between it is supposed
280 to be alive and the first bytes sent: this is a best effort to prevent the
281 backend from closing because of idle or keepalive timeout in the meantime.
282 Also, handle a new "proxy-flushall" environment variable which allows to
283 flush any forwarded body data immediately. PR 56541+37920.
284 trunk patch: http://svn.apache.org/r1656259
285 http://svn.apache.org/r1656359 (CHANGES entry)
286 2.4.x patch: trunk works (modulo CHANGES, docs/log-message-tags)
288 -0: jim: This seems to be a hit to normal performance, to handle an
289 error and/or non-normal condition. The pre-fetch is
290 expensive, and is always done, even before we know that
291 the backend is available to rec' it. I understand the
292 error described, but is the fix actually worth it (plus
293 it seems to allow for a DDoS vector).
294 ylavic: It seems to me that the problem is real since we reuse the
295 connection before prefetching 16K (either controlled by the
296 client, or by an input filter), we currently always prefetch
297 these bytes already. Regarding performance I don't see any
298 difference (more cycles) compared with the current code.
299 However I think I failed to rebuild the header_brigade when
300 the proxy loop is retried (ping), so I need to rework this.
301 Do you think we'd better remove the prefetch, or maybe just
302 make it nonblocking (by default)?
303 jim: Non-blocking seems the best way to handle...
305 * mod_dav: Allow other modules to become providers and add ACLs
306 to the DAV response. Requires a release of apr-util v1.6.
307 trunk patch: http://svn.apache.org/r1748322
308 2.4.x: trunk works modulo CHANGES/MMN
310 rpluem asks: Will this compile with apr-util < v1.6 and keep
311 mod_dav working (without the new features of the patch of course)?
312 I doubt that we will require apr-util 1.6 for the lifetime of 2.4.x
313 (see the discussion around ap_cstr_casecmp[n] an apr 1.6)
314 minfrin: Yes, as you can see in the patch everything applies only
315 if APR_XML_X2T_PARSED is defined, and the patch was tested with
316 both apr-util v1.6 and apr-util v1.5.
317 -1: jorton, breaks binary backwards compat per dev@ discuss
318 msgid <20160902120654.GA12674@redhat.com>
319 (& also, making the structure change with apr-util version
320 means it breaks binary compat across an apr-util upgrade?)
322 * Support PCRE2 (10.x) in place of PCRE (8.x).
323 Submitted by: wrowe, Petr Pisar [ppisar redhat.com]
325 http://svn.apache.org/r1773454
326 http://svn.apache.org/r1773741
327 http://svn.apache.org/r1773742
328 http://svn.apache.org/r1773839
329 http://svn.apache.org/r1773870
330 http://svn.apache.org/r1773882
331 wrowe notes that the current code is too inefficient, owing to the fact
332 that the ovector is a required allocation and is no longer allocated on
333 the stack, by design. The correct fix is an apr userdata allocation on
334 the appropriate pool, which would be thread-safe, but the actual API of
335 ap_regexec[_len]() offers us no pool. We cannot associate that pool with
336 the ap_regex_t, because a single regex may be used by many threads in
337 parallel and is not thread-safe beyond initialization.
338 So the only fix allowing us to use PCRE 10 in httpd 2.4 would be to write
339 this as a thread safe storage buffer for the majority of cases (<10 $args)
340 and we don't have a portable tls mechanism to do so.
343 PATCHES/ISSUES THAT ARE STALLED
345 * core: Add ap_errorlog_provider to make ErrorLog logging modular. This
346 backport keeps syslog logging as part of httpd core and only adds
347 API to allow other modules to be used for error logging.
348 trunk patch: http://svn.apache.org/r1525597
349 http://svn.apache.org/r1525664
350 http://svn.apache.org/r1525845
351 http://svn.apache.org/r1527003
352 http://svn.apache.org/r1527005
353 http://svn.apache.org/r1532344
354 http://svn.apache.org/r1539988
355 http://svn.apache.org/r1541029
356 http://svn.apache.org/r1543979
357 http://svn.apache.org/r1544156
358 http://svn.apache.org/r1626978
359 2.4.x patch: http://people.apache.org/~jkaluza/patches/httpd-2.4.x-errorlog_provider.patch
361 +1: covener w/ doc or code to fix syntax (providername:providerarg not supported like syslog or socacheproviders,
362 needs 2 args which is not valid in ErrorLog manual)
363 trawick: nit: fix "writing" in "/* NULL if we are writing to syslog */"
364 (sorry, haven't finished reviewing completely)
365 jim: What is the status of this??
367 * mod_proxy: Add ap_proxy_define_match_worker() and use it for ProxyPassMatch
368 and ProxyMatch section to distinguish between normal workers and workers
369 with regex substitutions in the name. Implement handling of such workers
370 in ap_proxy_get_worker(). Fixes the bug when regex workers were not
371 matched and used for request. PR 43513.
372 trunk patch: http://svn.apache.org/r1609680
373 http://svn.apache.org/r1609688
374 http://svn.apache.org/r1641381
375 ylavic: Merge patch provided (reusing new->real to avoid double de_socketfy() call).
376 Also added missing r1609688 to the patchset.
377 2.4.x patch: http://people.apache.org/~ylavic/httpd-2.4.x-ap_proxy_define_match_worker.patch
379 -0: covener tried to review this one in Austin with Jeff. Does the added match function
380 really cover a very narrow set of parameters with the way it skips over backreferences?
381 Also, why a new API vs. just setting the field inline?
383 * mod_systemd: New module, for integration with systemd on Linux.
384 trunk patch: http://svn.apache.org/r1393976
385 http://svn.apache.org/r1393997
386 http://svn.apache.org/r1484554
387 http://svn.apache.org/r1528032
388 http://svn.apache.org/r1528034
389 http://svn.apache.org/r1614821
390 http://svn.apache.org/r1618579
391 http://svn.apache.org/r1618588
392 2.4.x patch: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-mod_systemd.patch
394 sf comments: The IdleShutdown logic seems broken. Consider a single
395 active connection that is stalled for 10 seconds. That
396 connection will be broken after GracefulShutdownTimeout.
397 A better logic would be to check if there is any open
398 connection that is not in keep-alive state.
400 * core: Add support for systemd socket activation.
401 trunk patch: http://svn.apache.org/r1511033
402 http://svn.apache.org/r1608686
403 http://svn.apache.org/r1608694
404 http://svn.apache.org/r1608703
405 http://svn.apache.org/r1608721
406 http://svn.apache.org/r1608744
407 2.4.x patch: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-socket-activation.patch
410 * mod_proxy: Ensure network errors detected by the proxy are returned as
411 504 Gateway Timeout as opposed to 502 Bad Gateway
412 trunk patch: https://svn.apache.org/viewvc?view=revision&revision=1480058
413 2.4.x patch: trunk patch works modulo CHANGES
415 -1: rpluem: This change is still disputed. See
416 http://mail-archives.apache.org/mod_mbox/httpd-dev/201305.mbox/%3C1B16B9E3-87BA-4EEF-939C-7C7313B54714%40gbiv.com%3E
418 * cross-compile: allow to provide CC_FOR_BUILD so that gen_test_char will be
419 compiled by the build compiler instead of the host compiler.
420 Also set CC_FOR_BUILD to 'cc' when cross-compilation is detected.
421 Trunk patches: http://svn.apache.org/viewvc?view=revision&revision=1327907
422 http://svn.apache.org/viewvc?view=revision&revision=1328390
423 http://svn.apache.org/viewvc?view=revision&revision=1328714
424 2.4 patch: http://people.apache.org/~fuankg/diffs/httpd-2.4.x-cross_compile.diff
425 fuankg: on hold until we agree for a better and more simple solution ...
427 * Makefile.win: Added copying of .vbs / .wsf CGIs to Windows install target.
428 Moved fixing of shebang to separate target so that it is
429 no longer executed by default and all CGIs remain inactive.
430 trunk patch: http://svn.apache.org/viewvc?view=revision&revision=1387984
431 http://svn.apache.org/viewvc?view=revision&revision=1421203
432 http://svn.apache.org/viewvc?view=revision&revision=1421591
433 2.4.x patch: http://people.apache.org/~fuankg/diffs/httpd-2.4.x-Makefile.win.diff
436 This commit is essentially deciding that an httpd install on
437 Windows now has printenv/testcgi written in 2 more languages.
438 To the extent that the usefulness is that it shows how to make scripts
439 of these types executable by httpd, I believe that the documentation
440 is the proper place to solve that. To the extent that the usefullness
441 is to show how to implement a CGI in these particular languages, I believe
442 that the httpd distribution and documentation in general is not the
443 place for that. Historically these types of scripts have caused problems
444 for downstream vendorsas well as newbies (and sometimes the intersection
445 of those two groups) who don't understand that these are information leaks
446 once they are enabled, and the subtlety of the way they are disabled ("Apache
447 messed up the first line; let me fix that") contributes to that.
448 fuankg notes: I've just added a big warning to all CGI scripts which should now
449 make absolutely clear that these CGIs are for testing purpose only - so those
450 who enable those scripts with inserting the right shebang should be 100% aware
451 of any risks (this should cover your last point).
452 jim: trawick, does the above address your concerns?
453 trawick: to some extent (somebody reading the script gets an idea)
454 Why isn't the configuration requirement documented instead
455 of described indirectly in a sample?
456 Why are these new samples added to the install without three
457 votes? (I didn't veto it; put your name next to the two
458 existing ones and I'll be satisfied that enough people
459 considered this addition as an appropriate solution for a
460 real httpd usability problem.)
461 wrowe: I'd agree with trawick, and suggest that these scripts can begin
462 their life somewhere in the manual/ tree. This really seems like
463 the place where /usr/share/httpd/examples/ would be useful, but
464 there isn't an ordinary directory for that. Since we want none
465 of the scripts to function 'out of the box', what about a new
466 cgi-examples/ dir alongside cgi-bin/? Otherwise manual/cgi/examples
469 * core: block Define and Undefine in vhost and directory context. Because
470 it is EXEC_ON_READ, it "breaks out" of these contexts anyway.
471 trunk patch: http://svn.apache.org/r1656063
472 http://svn.apache.org/r1656122
473 2.4.x patch: http://people.apache.org/~covener/patches/2.4.x-define-limits.diff
474 +1: covener (I need to review the docs manually in this area)
475 -1: wrowe (blocking will break "working" .conf files on a subversion update
476 meant to pick up security fixes. "Alerting" I would agree to.)