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 Decmber 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. ]
117 PATCHES PROPOSED TO BACKPORT FROM TRUNK:
118 [ New proposals should be added at the end of the list ]
120 *) mod_alias: Introduce expression parser support for Alias, ScriptAlias
121 and Redirect. Limit Redirect expressions to directory (Location) context
122 and redirect statuses (implicit or explicit).
123 trunk patch: http://svn.apache.org/r1653941
124 http://svn.apache.org/r1653978
125 http://svn.apache.org/r1656225
126 http://svn.apache.org/r1686853
127 http://svn.apache.org/r1686856
128 2.4.x patch: https://people.apache.org/~minfrin/httpd-mod_alias-expr2.patch
131 *) mod_ssl: Free dhparams when getting DH params. This fixes issue when
132 SSLCryptoDevice does not get unregistered because of non-zero refcount
133 during the mod_ssl unload happening on httpd startup.
134 trunk patch: http://svn.apache.org/r1720129
135 2.4.x patch: http://jkaluza.fedorapeople.org/httpd-2.4.x-dhparams-free.patch
137 ylavic: +1 with r1723295 (likewise for ecparams).
139 *) mod_cache_socache: Fix a possible cached entity body corruption when it
140 is received from an origin server in multiple batches and forwarded by
142 trunk patch: http://svn.apache.org/r1721899
143 2.4.x patch: trunk works, module CHANGES
146 *) mod_ssl: Add SSLOCSPProxyURL to add the possibility to do all queries
147 to OCSP responders through a HTTP proxy.
148 Trunk version of patch:
149 http://svn.apache.org/r1726881
150 http://svn.apache.org/r1727111
151 Backport version for 2.4.x of patch:
152 Trunk version of patch works modulo CHANGES
155 *) mod_proxy_hcheck: Dynamic reverse proxy backend health check module
156 Trunk version of patch: <various>
157 Backport version for 2.4.x of patch:
158 http://home.apache.org/~jim/patches/hcheck-2.4.patch
162 *) core: Track the useragent_host per-request when mod_remoteip or similar
163 modules track a per-request useragent_ip. Modules should be updated
164 to inquire for ap_get_useragent_host() in place of ap_get_remote_host().
165 Trunk version of patch:
166 http://svn.apache.org/r1729929
167 Trunk patch to core.c/http_core.h applies, modulo CHANGES & ap_mmn.h
168 Note: httpd.h comment r.e. realiging bit fields must be omitted.
171 *) hostname: Test and log useragent_host per-request across various modules,
172 including the scoreboard, expression and rewrite engines, setenvif,
173 authz_host, access_compat, custom logging, ssl and REMOTE_HOST variables.
174 PR55348 [William Rowe]
175 Trunk version of patch:
176 http://svn.apache.org/r1729930
177 http://svn.apache.org/r1729931
178 Trunk patch r1729930 applies, modulo CHANGES
179 Backport patch to r1729931 is noted in the commit log message
180 Requires r1729929 to be applied.
183 *) core: introducing new hook "pre_close_connection" to give protocols other
184 than http/1.1 a chance to send one last frame before close. Scoreboard
185 additions to allow update from master connections.
187 trunk patch: http://svn.apache.org/r1727071
188 http://svn.apache.org/r1727573
189 2.4.x patch: trunk works (modulo CHANGES)
190 covener: needs MMN bump, but sorting out previous MMN question first.
191 jim: Status, re: MMN bump ??
192 icing: I am embarrassingly bad at this. I propose to include the scoreboard
193 additions into this bump and propose all this together. So the new
194 proposal is (including an old apr_time_now() optimization from jim
195 for scorebaord.c). And that now includes all backports necessary to
196 update mod_http2 in 2.4.x:
198 http://svn.apache.org/r1417440
199 http://svn.apache.org/r1727071
200 http://svn.apache.org/r1727573
201 http://svn.apache.org/r1726009
202 http://svn.apache.org/r1726026
203 http://svn.apache.org/r1729376
204 http://svn.apache.org/r1729960
205 2.4.x patch: trunk works (modulo CHANGES)
209 *) mod_watchdog: Error logging
210 trunk patch: http://svn.apache.org/r1722154
211 http://svn.apache.org/r1722701
212 2.4.x patch: trunk works
216 trunk patch: http://svn.apache.org/r1725485
217 2.4.x patch: trunk works
218 http://home.apache.org/~jim/patches/aplogno-2.4.patch
221 *) mod_heartmonitor: No need to search twice for the same value + fix some style
222 trunk patch: http://svn.apache.org/r1727842
223 2.4.x patch: trunk works
226 *) mod_proxy_wstunnel, mod_proxy_connect: Use the correct pool and allocator
227 lifetime when sending brigades and buckets down the filter chain to the
228 backend and the client in mod_proxy_wstunnel and mod_proxy_connect.
229 Trunk version of patch:
230 http://svn.apache.org/r1726776
231 http://svn.apache.org/r1726779
232 http://svn.apache.org/r1726781
233 http://svn.apache.org/r1726782
234 http://svn.apache.org/r1726787
235 http://svn.apache.org/r1727551
236 http://svn.apache.org/r1727553
237 http://svn.apache.org/r1727567
238 http://svn.apache.org/r1728478
239 http://svn.apache.org/r1728481
240 http://svn.apache.org/r1730823
241 Backport version for 2.4.x of patch:
242 http://home.apache.org/~rpluem/patches/proxy_correctlifetime.diff
245 PATCHES/ISSUES THAT ARE BEING WORKED
247 * core: Fix crash in ap_mpm_pod_check call caused by NULL dereference of
248 its parameter when starting httpd as single process (httpd -X).
249 trunk patch: http://svn.apache.org/r1711479
250 2.4.x patch: trunk works
252 minfrin: Needs extra parens to suppress a warning:
253 prefork.c:1319:16: note: place parentheses around the assignment
254 to silence this warning
255 jailletc36: This has been done in r1711919
256 ylavic: Also, I don't think the changes on worker/event are needed,
257 only prefork requires the accept mutex in ONE_PROCESS mode.
259 *) http: Don't remove the Content-Length of zero from a HEAD response if
260 it comes from an origin server, module or script. Allow the previous
261 behaviour (for legacy/buggy modules only, not origin) by also backporting
262 the HttpContentLengthHeadZero directive (and also HttpExpectStrict which
263 comes for free with the same commit).
264 trunk patch: http://svn.apache.org/r1554303
265 http://svn.apache.org/r1678215
266 2.4.x patch: http://people.apache.org/~ylavic/httpd-2.4.x-preserve_head_cl_zero.patch
268 ylavic: r1554303 issued a major MMN bump, but since the ABI change is two
269 ints added at the end of core_server_config, the proposed merge
270 does a minor bump only.
271 minfrin: Two new directives need to be documented.
273 * mod_proxy_http: Don't establish or reuse a backend connection before pre-
274 fetching the request body, so to minimize the delay between it is supposed
275 to be alive and the first bytes sent: this is a best effort to prevent the
276 backend from closing because of idle or keepalive timeout in the meantime.
277 Also, handle a new "proxy-flushall" environment variable which allows to
278 flush any forwarded body data immediately. PR 56541+37920.
279 trunk patch: http://svn.apache.org/r1656259
280 http://svn.apache.org/r1656359 (CHANGES entry)
281 2.4.x patch: trunk works (modulo CHANGES, docs/log-message-tags)
283 -0: jim: This seems to be a hit to normal performance, to handle an
284 error and/or non-normal condition. The pre-fetch is
285 expensive, and is always done, even before we know that
286 the backend is available to rec' it. I understand the
287 error described, but is the fix actually worth it (plus
288 it seems to allow for a DDoS vector).
289 ylavic: It seems to me that the problem is real since we reuse the
290 connection before prefetching 16K (either controlled by the
291 client, or by an input filter), we currently always prefetch
292 these bytes already. Regarding performance I don't see any
293 difference (more cycles) compared with the current code.
294 However I think I failed to rebuild the header_brigade when
295 the proxy loop is retried (ping), so I need to rework this.
296 Do you think we'd better remove the prefetch, or maybe just
297 make it nonblocking (by default)?
298 jim: Non-blocking seems the best way to handle...
300 PATCHES/ISSUES THAT ARE STALLED
302 * core: Add ap_errorlog_provider to make ErrorLog logging modular. This
303 backport keeps syslog logging as part of httpd core and only adds
304 API to allow other modules to be used for error logging.
305 trunk patch: http://svn.apache.org/r1525597
306 http://svn.apache.org/r1525664
307 http://svn.apache.org/r1525845
308 http://svn.apache.org/r1527003
309 http://svn.apache.org/r1527005
310 http://svn.apache.org/r1532344
311 http://svn.apache.org/r1539988
312 http://svn.apache.org/r1541029
313 http://svn.apache.org/r1543979
314 http://svn.apache.org/r1544156
315 http://svn.apache.org/r1626978
316 2.4.x patch: http://people.apache.org/~jkaluza/patches/httpd-2.4.x-errorlog_provider.patch
318 +1: covener w/ doc or code to fix syntax (providername:providerarg not supported like syslog or socacheproviders,
319 needs 2 args which is not valid in ErrorLog manual)
320 trawick: nit: fix "writing" in "/* NULL if we are writting to syslog */"
321 (sorry, haven't finished reviewing completely)
322 jim: What is the status of this??
324 * mod_proxy: Add ap_proxy_define_match_worker() and use it for ProxyPassMatch
325 and ProxyMatch section to distinguish between normal workers and workers
326 with regex substitutions in the name. Implement handling of such workers
327 in ap_proxy_get_worker(). Fixes the bug when regex workers were not
328 matched and used for request. PR 43513.
329 trunk patch: http://svn.apache.org/r1609680
330 http://svn.apache.org/r1609688
331 http://svn.apache.org/r1641381
332 ylavic: Merge patch provided (reusing new->real to avoid double de_socketfy() call).
333 Also added missing r1609688 to the patchset.
334 2.4.x patch: http://people.apache.org/~ylavic/httpd-2.4.x-ap_proxy_define_match_worker.patch
336 -0: covener tried to review this one in Austin with Jeff. Does the added match function
337 really cover a very narrow set of parameters with the way it skips over backreferences?
338 Also, why a new API vs. just setting the field inline?
340 * mod_systemd: New module, for integration with systemd on Linux.
341 trunk patch: http://svn.apache.org/r1393976
342 http://svn.apache.org/r1393997
343 http://svn.apache.org/r1484554
344 http://svn.apache.org/r1528032
345 http://svn.apache.org/r1528034
346 http://svn.apache.org/r1614821
347 http://svn.apache.org/r1618579
348 http://svn.apache.org/r1618588
349 2.4.x patch: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-mod_systemd.patch
352 * mod_journald: Add new module mod_journald to log error logs into journald.
353 This patch needs changes done in mod_systemd patch (already
355 trunk patch: http://svn.apache.org/r1610339
356 http://svn.apache.org/r1621806
357 2.4.x patch: http://people.apache.org/~jkaluza/patches/httpd-2.4.x-mod_journald.patch
359 rjung, minfrin: Not understanding "This patch needs changes done in
360 mod_systemd patch", am I right in understanding this patch is
362 jkaluza: No, that patch is not committed yet. It is in STALLED section.
363 The link for that patch is: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-mod_systemd.patch
365 * core: Add support for systemd socket activation.
366 trunk patch: http://svn.apache.org/r1511033
367 http://svn.apache.org/r1608686
368 http://svn.apache.org/r1608694
369 http://svn.apache.org/r1608703
370 http://svn.apache.org/r1608721
371 http://svn.apache.org/r1608744
372 2.4.x patch: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-socket-activation.patch
375 * mod_proxy: Ensure network errors detected by the proxy are returned as
376 504 Gateway Timout as opposed to 502 Bad Gateway
377 trunk patch: https://svn.apache.org/viewvc?view=revision&revision=1480058
378 2.4.x patch: trunk patch works modulo CHANGES
380 -1: rpluem: This change is still disputed. See
381 http://mail-archives.apache.org/mod_mbox/httpd-dev/201305.mbox/%3C1B16B9E3-87BA-4EEF-939C-7C7313B54714%40gbiv.com%3E
383 * cross-compile: allow to provide CC_FOR_BUILD so that gen_test_char will be
384 compiled by the build compiler instead of the host compiler.
385 Also set CC_FOR_BUILD to 'cc' when cross-compilation is detected.
386 Trunk patches: http://svn.apache.org/viewvc?view=revision&revision=1327907
387 http://svn.apache.org/viewvc?view=revision&revision=1328390
388 http://svn.apache.org/viewvc?view=revision&revision=1328714
389 2.4 patch: http://people.apache.org/~fuankg/diffs/httpd-2.4.x-cross_compile.diff
390 fuankg: on hold until we agree for a better and more simple solution ...
392 * Makefile.win: Added copying of .vbs / .wsf CGIs to Windows install target.
393 Moved fixing of shebang to separate target so that it is
394 no longer executed by default and all CGIs remain inactive.
395 trunk patch: http://svn.apache.org/viewvc?view=revision&revision=1387984
396 http://svn.apache.org/viewvc?view=revision&revision=1421203
397 http://svn.apache.org/viewvc?view=revision&revision=1421591
398 2.4.x patch: http://people.apache.org/~fuankg/diffs/httpd-2.4.x-Makefile.win.diff
401 This commit is essentially deciding that an httpd install on
402 Windows now has printenv/testcgi written in 2 more languages.
403 To the extent that the usefulness is that it shows how to make scripts
404 of these types executable by httpd, I believe that the documentation
405 is the proper place to solve that. To the extent that the usefullness
406 is to show how to implement a CGI in these particular languages, I believe
407 that the httpd distribution and documentation in general is not the
408 place for that. Historically these types of scripts have caused problems
409 for downstream vendorsas well as newbies (and sometimes the intersection
410 of those two groups) who don't understand that these are information leaks
411 once they are enabled, and the subtlety of the way they are disabled ("Apache
412 messed up the first line; let me fix that") contributes to that.
413 fuankg notes: I've just added a big warning to all CGI scripts which should now
414 make absolutely clear that these CGIs are for testing purpose only - so those
415 who enable those scripts with inserting the right shebang should be 100% aware
416 of any risks (this should cover your last point).
417 jim: trawick, does the above address your concerns?
418 trawick: to some extent (somebody reading the script gets an idea)
419 Why isn't the configuration requirement documented instead
420 of described indirectly in a sample?
421 Why are these new samples added to the install without three
422 votes? (I didn't veto it; put your name next to the two
423 existing ones and I'll be satisified that enough people
424 considered this addition as an appropriate solution for a
425 real httpd usability problem.)
426 wrowe: I'd agree with trawick, and suggest that these scripts can begin
427 their life somewhere in the manual/ tree. This really seems like
428 the place where /usr/share/httpd/examples/ would be useful, but
429 there isn't an ordinary directory for that. Since we want none
430 of the scripts to function 'out of the box', what about a new
431 cgi-examples/ dir alongside cgi-bin/? Otherwise manual/cgi/examples