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.
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:
116 *) configure.in: Latest macOS Xcode 9 installs clang-900, which more
117 fully honors strict-prototypes, which causes AC_CHECK_LIB to
118 fail when --enable-maintainer-mode is set.
119 trunk patch: http://svn.apache.org/r1810448
120 2.4.x patch: svn merge -c 1810448 ^/httpd/httpd/trunk .
123 PATCHES ACCEPTED TO BACKPORT FROM TRUNK:
124 [ start all new proposals below, under PATCHES PROPOSED. ]
126 *) mod_authz_dbd: Fix a segmentation fault if AuthzDBDQuery is not set.
128 trunk patch: http://svn.apache.org/r1809209
129 2.4.x patch: svn merge -c 1809209 ^/httpd/httpd/trunk .
130 +1: jailletc36 (by inspection), ylavic, elukey
132 *) mod_http2: Fix race condition on request body handlign.
133 2.4.x patch: svn merge -c 1804096,1807238,1809981,1810088,1810089 ^/httpd/httpd/trunk .
134 +1: icing, steffenal, ylavic
137 PATCHES PROPOSED TO BACKPORT FROM TRUNK:
138 [ New proposals should be added at the end of the list ]
140 *) mod_proxy, mod_ssl: Handle SSLProxy* directives in <Proxy> sections,
141 allowing per backend TLS configuration.
142 trunk patch: http://svn.apache.org/r1740928
143 http://svn.apache.org/r1740960
144 http://svn.apache.org/r1740967
145 http://svn.apache.org/r1740987
146 http://svn.apache.org/r1740998
147 http://svn.apache.org/r1742697
148 http://svn.apache.org/r1756976
149 http://svn.apache.org/r1781313
150 2.4.x patch: http://home.apache.org/~ylavic/patches/httpd-2.4.x-r1740928_and_co-v3.patch
152 mrumph: Since this has been sitting for awhile, there are several places
153 where this patch needs to be adjusted against recent changes to 2.4.x.
154 ylavic: With current 2.4.x (r1807662), there seems to be only a conflict with
155 MMN, which can probably be taken by the backporter. I don't see the
156 other places where it needs adjustments, Mike?
158 *) mod_remoteip: Add PROXY protocol support
159 trunk patch: http://svn.apache.org/r1776575
160 http://svn.apache.org/r1776578 (doc fix)
161 http://svn.apache.org/r1776627 (shortened name + doc fix)
162 http://svn.apache.org/r1776674 (attribution moved to CHANGES)
163 http://svn.apache.org/r1776740 (attribution updated in mod_remotip.c)
164 http://svn.apache.org/r1778268 (fix compiler warning)
165 http://svn.apache.org/r1780725 (set buckets aside)
166 http://svn.apache.org/r1781030 (fix strict GCC warning)
167 http://svn.apache.org/r1781031 (reference the filter by handle)
168 http://svn.apache.org/r1781701 (rework optional processing case)
169 http://svn.apache.org/r1788674 (final edge cases/ignore slave conns)
170 http://svn.apache.org/r1789800 (remove optional processing)
171 http://svn.apache.org/r1790169 (rename "exception" directive)
172 http://svn.apache.org/r1790457 (Update directive name in err message)
173 http://svn.apache.org/r1806985
174 2.4 convenience patch (includes CHANGES):
175 http://home.apache.org/~jim/patches/RemoteIPProxyProtocol.2.4.x.patch
176 http://svn.apache.org/r1806985
178 mrumph: I had a chance to review this proposal.
179 I committed some suggested changes to trunk in r1806985.
180 Also, the copyright in mod_remoteip.c is of some concern.
181 Perhaps the terms of the copyright should be included in that note.
182 And on a personal note, today is my last day with Oracle.
183 So it may well be my last day with Apache as well.
184 It has been great working with all of you.
185 jim: Not sure what the copyright concern is, but added r1806985
187 ylavic: RemoteIPProxyProtocol* are documented as scoped to server config
188 and virtual host, though using ap_server_conf makes them global
189 only (thus less useful too...).
191 *) mod_journald: Add new module mod_journald to log error logs into journald.
192 trunk patch: http://svn.apache.org/r1610339
193 http://svn.apache.org/r1621806
194 2.4.x patch: http://people.apache.org/~jkaluza/patches/httpd-2.4.x-mod_journald.patch
196 jchampion: Looks like the headers require GCC extensions to compile, so
197 mod_journald can't be configured in maintainer mode (-std=c89).
198 Can anyone else reproduce, or is it just my distro?
200 *) Quiet spurious gcc warning in ap_parse_form_data
201 trunk patch: http://svn.apache.org/r1798785
202 2.4.x patch: svn merge -c 1798785 ^/httpd/httpd/trunk .
203 +1: jailletc36, ylavic
205 *) mod_rewrite,core: Avoid the 'Vary: Host' response header when HTTP_HOST
206 is used in a condition that evaluates to true.
207 trunk patch: http://svn.apache.org/r1808746
208 http://svn.apache.org/r1809028
209 2.4.x patch: svn merge -c 1808746,1809028 ^/httpd/httpd/trunk .
212 PATCHES/ISSUES THAT ARE BEING WORKED
213 [ New entries should be added at the START of the list ]
215 *) mod_ssl: Return 502 instead of 500 when SSL peer check or
216 proxy_post_handshake hook fails.
217 Trunk patch: r1645529 (works)
218 2.4.x patch which adds CHANGES: https://emptyhammock.com/media/downloads/r1645529-to-2.4.x.txt
220 ylavic: there may be missing bits, see thread for commit r1736510.
222 *) core: Drop an invalid Last-Modified header value coming
223 from a (F)CGI script instead of replacing it with Unix epoch.
224 Warn the users about Last-Modified header value replacements
225 and violations of the RFC.
226 trunk patch: http://svn.apache.org/r1748379
227 http://svn.apache.org/r1750747
228 http://svn.apache.org/r1750749
229 http://svn.apache.org/r1750953
230 http://svn.apache.org/r1751138
231 http://svn.apache.org/r1751139
232 http://svn.apache.org/r1751147
233 http://svn.apache.org/r1757818
234 2.4.x: trunk patches work, final view:
235 http://home.apache.org/~elukey/httpd-2.4.x-core-last_modified_tz_logging.patch
236 The problem has been discussed in dev@ extensively but we did not reach a common
237 agreement about how to proceed in the long term. While we wait, I would really like
238 to introduce useful logs for the users (the starting point of this change was a users@
239 email thread). If this is not the right way to go I will move the patch to other
240 sections of STATUS (stalled or being worked).
241 The code has been tested with a simple PHP script returning different Last-Modified
242 headers (GMT now, GMT now Europe/Paris, GMT tomorrow, GMT yesterday, PST now).
245 *) http: Don't remove the Content-Length of zero from a HEAD response if
246 it comes from an origin server, module or script. Allow the previous
247 behaviour (for legacy/buggy modules only, not origin) by also backporting
248 the HttpContentLengthHeadZero directive (and also HttpExpectStrict which
249 comes for free with the same commit).
250 trunk patch: http://svn.apache.org/r1554303
251 http://svn.apache.org/r1678215
252 2.4.x patch: http://people.apache.org/~ylavic/httpd-2.4.x-preserve_head_cl_zero.patch
254 ylavic: r1554303 issued a major MMN bump, but since the ABI change is two
255 ints added at the end of core_server_config, the proposed merge
256 does a minor bump only.
257 minfrin: Two new directives need to be documented.
259 * mod_proxy_http: Don't establish or reuse a backend connection before pre-
260 fetching the request body, so to minimize the delay between it is supposed
261 to be alive and the first bytes sent: this is a best effort to prevent the
262 backend from closing because of idle or keepalive timeout in the meantime.
263 Also, handle a new "proxy-flushall" environment variable which allows to
264 flush any forwarded body data immediately. PR 56541+37920.
265 trunk patch: http://svn.apache.org/r1656259
266 http://svn.apache.org/r1656359 (CHANGES entry)
267 2.4.x patch: trunk works (modulo CHANGES, docs/log-message-tags)
269 -0: jim: This seems to be a hit to normal performance, to handle an
270 error and/or non-normal condition. The pre-fetch is
271 expensive, and is always done, even before we know that
272 the backend is available to rec' it. I understand the
273 error described, but is the fix actually worth it (plus
274 it seems to allow for a DDoS vector).
275 ylavic: It seems to me that the problem is real since we reuse the
276 connection before prefetching 16K (either controlled by the
277 client, or by an input filter), we currently always prefetch
278 these bytes already. Regarding performance I don't see any
279 difference (more cycles) compared with the current code.
280 However I think I failed to rebuild the header_brigade when
281 the proxy loop is retried (ping), so I need to rework this.
282 Do you think we'd better remove the prefetch, or maybe just
283 make it nonblocking (by default)?
284 jim: Non-blocking seems the best way to handle...
286 * mod_dav: Allow other modules to become providers and add ACLs
287 to the DAV response. Requires a release of apr-util v1.6.
288 trunk patch: http://svn.apache.org/r1748322
289 2.4.x: trunk works modulo CHANGES/MMN
291 rpluem asks: Will this compile with apr-util < v1.6 and keep
292 mod_dav working (without the new features of the patch of course)?
293 I doubt that we will require apr-util 1.6 for the lifetime of 2.4.x
294 (see the discussion around ap_cstr_casecmp[n] an apr 1.6)
295 minfrin: Yes, as you can see in the patch everything applies only
296 if APR_XML_X2T_PARSED is defined, and the patch was tested with
297 both apr-util v1.6 and apr-util v1.5.
298 -1: jorton, breaks binary backwards compat per dev@ discuss
299 msgid <20160902120654.GA12674@redhat.com>
300 (& also, making the structure change with apr-util version
301 means it breaks binary compat across an apr-util upgrade?)
303 * Support PCRE2 (10.x) in place of PCRE (8.x).
304 Submitted by: wrowe, Petr Pisar [ppisar redhat.com]
306 http://svn.apache.org/r1773454
307 http://svn.apache.org/r1773741
308 http://svn.apache.org/r1773742
309 http://svn.apache.org/r1773839
310 http://svn.apache.org/r1773870
311 http://svn.apache.org/r1773882
312 wrowe notes that the current code is too inefficient, owing to the fact
313 that the ovector is a required allocation and is no longer allocated on
314 the stack, by design. The correct fix is an apr userdata allocation on
315 the appropriate pool, which would be thread-safe, but the actual API of
316 ap_regexec[_len]() offers us no pool. We cannot associate that pool with
317 the ap_regex_t, because a single regex may be used by many threads in
318 parallel and is not thread-safe beyond initialization.
319 So the only fix allowing us to use PCRE 10 in httpd 2.4 would be to write
320 this as a thread safe storage buffer for the majority of cases (<10 $args)
321 and we don't have a portable tls mechanism to do so.
324 PATCHES/ISSUES THAT ARE STALLED
326 * core: Add ap_errorlog_provider to make ErrorLog logging modular. This
327 backport keeps syslog logging as part of httpd core and only adds
328 API to allow other modules to be used for error logging.
329 trunk patch: http://svn.apache.org/r1525597
330 http://svn.apache.org/r1525664
331 http://svn.apache.org/r1525845
332 http://svn.apache.org/r1527003
333 http://svn.apache.org/r1527005
334 http://svn.apache.org/r1532344
335 http://svn.apache.org/r1539988
336 http://svn.apache.org/r1541029
337 http://svn.apache.org/r1543979
338 http://svn.apache.org/r1544156
339 http://svn.apache.org/r1626978
340 2.4.x patch: http://people.apache.org/~jkaluza/patches/httpd-2.4.x-errorlog_provider.patch
342 +1: covener w/ doc or code to fix syntax (providername:providerarg not supported like syslog or socacheproviders,
343 needs 2 args which is not valid in ErrorLog manual)
344 trawick: nit: fix "writing" in "/* NULL if we are writing to syslog */"
345 (sorry, haven't finished reviewing completely)
346 jim: What is the status of this??
348 * mod_proxy: Add ap_proxy_define_match_worker() and use it for ProxyPassMatch
349 and ProxyMatch section to distinguish between normal workers and workers
350 with regex substitutions in the name. Implement handling of such workers
351 in ap_proxy_get_worker(). Fixes the bug when regex workers were not
352 matched and used for request. PR 43513.
353 trunk patch: http://svn.apache.org/r1609680
354 http://svn.apache.org/r1609688
355 http://svn.apache.org/r1641381
356 ylavic: Merge patch provided (reusing new->real to avoid double de_socketfy() call).
357 Also added missing r1609688 to the patchset.
358 2.4.x patch: http://people.apache.org/~ylavic/httpd-2.4.x-ap_proxy_define_match_worker.patch
360 -0: covener tried to review this one in Austin with Jeff. Does the added match function
361 really cover a very narrow set of parameters with the way it skips over backreferences?
362 Also, why a new API vs. just setting the field inline?
364 * mod_systemd: New module, for integration with systemd on Linux.
365 trunk patch: http://svn.apache.org/r1393976
366 http://svn.apache.org/r1393997
367 http://svn.apache.org/r1484554
368 http://svn.apache.org/r1528032
369 http://svn.apache.org/r1528034
370 http://svn.apache.org/r1614821
371 http://svn.apache.org/r1618579
372 http://svn.apache.org/r1618588
373 2.4.x patch: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-mod_systemd.patch
375 sf comments: The IdleShutdown logic seems broken. Consider a single
376 active connection that is stalled for 10 seconds. That
377 connection will be broken after GracefulShutdownTimeout.
378 A better logic would be to check if there is any open
379 connection that is not in keep-alive state.
381 * core: Add support for systemd socket activation.
382 trunk patch: http://svn.apache.org/r1511033
383 http://svn.apache.org/r1608686
384 http://svn.apache.org/r1608694
385 http://svn.apache.org/r1608703
386 http://svn.apache.org/r1608721
387 http://svn.apache.org/r1608744
388 2.4.x patch: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-socket-activation.patch
391 * mod_proxy: Ensure network errors detected by the proxy are returned as
392 504 Gateway Timeout as opposed to 502 Bad Gateway
393 trunk patch: https://svn.apache.org/viewvc?view=revision&revision=1480058
394 2.4.x patch: trunk patch works modulo CHANGES
396 -1: rpluem: This change is still disputed. See
397 http://mail-archives.apache.org/mod_mbox/httpd-dev/201305.mbox/%3C1B16B9E3-87BA-4EEF-939C-7C7313B54714%40gbiv.com%3E
399 * cross-compile: allow to provide CC_FOR_BUILD so that gen_test_char will be
400 compiled by the build compiler instead of the host compiler.
401 Also set CC_FOR_BUILD to 'cc' when cross-compilation is detected.
402 Trunk patches: http://svn.apache.org/viewvc?view=revision&revision=1327907
403 http://svn.apache.org/viewvc?view=revision&revision=1328390
404 http://svn.apache.org/viewvc?view=revision&revision=1328714
405 2.4 patch: http://people.apache.org/~fuankg/diffs/httpd-2.4.x-cross_compile.diff
406 fuankg: on hold until we agree for a better and more simple solution ...
408 * Makefile.win: Added copying of .vbs / .wsf CGIs to Windows install target.
409 Moved fixing of shebang to separate target so that it is
410 no longer executed by default and all CGIs remain inactive.
411 trunk patch: http://svn.apache.org/viewvc?view=revision&revision=1387984
412 http://svn.apache.org/viewvc?view=revision&revision=1421203
413 http://svn.apache.org/viewvc?view=revision&revision=1421591
414 2.4.x patch: http://people.apache.org/~fuankg/diffs/httpd-2.4.x-Makefile.win.diff
417 This commit is essentially deciding that an httpd install on
418 Windows now has printenv/testcgi written in 2 more languages.
419 To the extent that the usefulness is that it shows how to make scripts
420 of these types executable by httpd, I believe that the documentation
421 is the proper place to solve that. To the extent that the usefullness
422 is to show how to implement a CGI in these particular languages, I believe
423 that the httpd distribution and documentation in general is not the
424 place for that. Historically these types of scripts have caused problems
425 for downstream vendorsas well as newbies (and sometimes the intersection
426 of those two groups) who don't understand that these are information leaks
427 once they are enabled, and the subtlety of the way they are disabled ("Apache
428 messed up the first line; let me fix that") contributes to that.
429 fuankg notes: I've just added a big warning to all CGI scripts which should now
430 make absolutely clear that these CGIs are for testing purpose only - so those
431 who enable those scripts with inserting the right shebang should be 100% aware
432 of any risks (this should cover your last point).
433 jim: trawick, does the above address your concerns?
434 trawick: to some extent (somebody reading the script gets an idea)
435 Why isn't the configuration requirement documented instead
436 of described indirectly in a sample?
437 Why are these new samples added to the install without three
438 votes? (I didn't veto it; put your name next to the two
439 existing ones and I'll be satisfied that enough people
440 considered this addition as an appropriate solution for a
441 real httpd usability problem.)
442 wrowe: I'd agree with trawick, and suggest that these scripts can begin
443 their life somewhere in the manual/ tree. This really seems like
444 the place where /usr/share/httpd/examples/ would be useful, but
445 there isn't an ordinary directory for that. Since we want none
446 of the scripts to function 'out of the box', what about a new
447 cgi-examples/ dir alongside cgi-bin/? Otherwise manual/cgi/examples
450 * core: block Define and Undefine in vhost and directory context. Because
451 it is EXEC_ON_READ, it "breaks out" of these contexts anyway.
452 trunk patch: http://svn.apache.org/r1656063
453 http://svn.apache.org/r1656122
454 2.4.x patch: http://people.apache.org/~covener/patches/2.4.x-define-limits.diff
455 +1: covener (I need to review the docs manually in this area)
456 -1: wrowe (blocking will break "working" .conf files on a subversion update
457 meant to pick up security fixes. "Alerting" I would agree to.)