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.
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 * core: Fix crash in ap_mpm_pod_check call caused by NULL dereference of
132 its parameter when starting httpd as single process (httpd -X).
133 trunk patch: http://svn.apache.org/r1711479
134 2.4.x patch: trunk works
136 minfrin: Needs extra parens to suppress a warning:
137 prefork.c:1319:16: note: place parentheses around the assignment
138 to silence this warning
139 jailletc36: This has been done in r1711919
140 ylavic: Also, I don't think the changes on worker/event are needed,
141 prefork only requires the accept mutex in ONE_PROCESS mode.
143 *) mod_ssl: Fix missing TLS Upgrade/Connection headers on OPTIONS * requests
144 (Note that this is simply a necessary band-aid, and still won't allow h2c
145 to peacefully coexist with tls/n.n upgrades, because Upgrade phase needs
146 to come earlier, not as a handler, and the bogus connection-close behavior
147 must be removed before the Protocol API can handle TLS upgrade.)
149 trunk patch: http://svn.apache.org/r1717816
151 ylavic: how about adding !ap_request_has_body(r) to the test then?
152 wrowe responds: nonstarter, as discussed on list.
154 *) mod_ssl: Free dhparams when getting DH params. This fixes issue when
155 SSLCryptoDevice does not get unregistered because of non-zero refcount
156 during the mod_ssl unload happening on httpd startup.
157 trunk patch: http://svn.apache.org/r1720129
158 2.4.x patch: http://jkaluza.fedorapeople.org/httpd-2.4.x-dhparams-free.patch
161 *) mod_cache_socache: Fix a possible cached entity body corruption when it
162 is received from an origin server in multiple batches and forwarded by
164 trunk patch: http://svn.apache.org/r1721899
165 2.4.x patch: trunk works, module CHANGES
168 *) core: Add expression support to SetHandler (someone wanted this in
169 a well-articulated serverfault post).
170 trunk patch: http://svn.apache.org/r1725149
171 http://svn.apache.org/r1725151
172 http://svn.apache.org/r1726233
173 2.4.x patch: MMN/changes only: http://people.apache.org/~covener/patches/2.4.x-sethandler-expr-2.diff
176 *) Add APLOGNO, first chunk (those that were detected by coccinelle).
177 There are some more but they are easier to backport once these here are applied.
178 trunk patch: http://svn.apache.org/r1725392 (modules)
179 http://svn.apache.org/r1725394 (server/mpm)
180 http://svn.apache.org/r1725395 (server others)
181 http://svn.apache.org/r1725468 (remove APLOGNO from mod_log_debug custom messages)
182 2.4.x patch: http://people.apache.org/~rjung/patches/aplogno-backport-r1725392.patch
183 http://people.apache.org/~rjung/patches/aplogno-backport-r1725394.patch
184 http://people.apache.org/~rjung/patches/aplogno-backport-r1725395.patch
185 http://people.apache.org/~rjung/patches/aplogno-backport-r1725468.patch
187 icing: needs http://svn.apache.org/r1725468
188 rjung: You are right, I added r1725468 and restart the vote.
189 @Jim: Only r1725468 is new: removing the added APLOGNO from
190 mod_log_debug where we actually log the configured custom
191 log messages. Admins can provide their own LOGNO as part
192 of the ocnfigured log message. It doesn't make sense to
195 *) mod_ssl: handle APR_TIMEUP on empty input by keeping connection state valid
197 trunk patch: http://svn.apache.org/r1725940
200 *) When more than one module calls APACHE_CHECK_OPENSSL, MOD_LDFLAGS and MOD_CFLAGS
201 remain unset for second or later caller. Fix this by caching the values for
202 MOD_LDFLAGS and MOD_CFLAGS created during the first run and set them in the
203 cached case. Change by rpluem
204 trunk patch: http://svn.apache.org/r1725325
205 2.4.x patch: trunk works
208 *) core: introducing new hook "pre_close_connection" to give protocols other
209 than http/1.1 a chance to send one last frame before close.
211 trunk patch: http://svn.apache.org/r1727071
212 http://svn.apache.org/r1727573
213 2.4.x patch: trunk works (modulo CHANGES)
216 *) core: Prevent a server crash in case of an invalid CONNECT request with
217 a custom error page for status code 400 that uses server side includes.
219 Trunk version of patch:
220 http://svn.apache.org/r1727544
221 Backport version for 2.4.x of patch:
222 Trunk version of patch works modulo CHANGES
225 *) mod_ssl: Add SSLOCSPProxyURL to add the possibility to do all queries
226 to OCSP responders through a HTTP proxy.
227 Trunk version of patch:
228 http://svn.apache.org/r1726881
229 http://svn.apache.org/r1727111
230 Backport version for 2.4.x of patch:
231 Trunk version of patch works modulo CHANGES
234 *) mod_proxy_hcheck: Dynamic reverse proxy backend health check module
235 Trunk version of patch:
236 Backport version for 2.4.x of patch:
239 PATCHES/ISSUES THAT ARE BEING WORKED
241 *) http: Don't remove the Content-Length of zero from a HEAD response if
242 it comes from an origin server, module or script. Allow the previous
243 behaviour (for legacy/buggy modules only, not origin) by also backporting
244 the HttpContentLengthHeadZero directive (and also HttpExpectStrict which
245 comes for free with the same commit).
246 trunk patch: http://svn.apache.org/r1554303
247 http://svn.apache.org/r1678215
248 2.4.x patch: http://people.apache.org/~ylavic/httpd-2.4.x-preserve_head_cl_zero.patch
250 ylavic: r1554303 issued a major MMN bump, but since the ABI change is two
251 ints added at the end of core_server_config, the proposed merge
252 does a minor bump only.
253 minfrin: Two new directives need to be documented.
255 * mod_proxy_http: Don't establish or reuse a backend connection before pre-
256 fetching the request body, so to minimize the delay between it is supposed
257 to be alive and the first bytes sent: this is a best effort to prevent the
258 backend from closing because of idle or keepalive timeout in the meantime.
259 Also, handle a new "proxy-flushall" environment variable which allows to
260 flush any forwarded body data immediately. PR 56541+37920.
261 trunk patch: http://svn.apache.org/r1656259
262 http://svn.apache.org/r1656359 (CHANGES entry)
263 2.4.x patch: trunk works (modulo CHANGES, docs/log-message-tags)
265 -0: jim: This seems to be a hit to normal performance, to handle an
266 error and/or non-normal condition. The pre-fetch is
267 expensive, and is always done, even before we know that
268 the backend is available to rec' it. I understand the
269 error described, but is the fix actually worth it (plus
270 it seems to allow for a DDoS vector).
271 ylavic: It seems to me that the problem is real since we reuse the
272 connection before prefetching 16K (either controlled by the
273 client, or by an input filter), we currently always prefetch
274 these bytes already. Regarding performance I don't see any
275 difference (more cycles) compared with the current code.
276 However I think I failed to rebuild the header_brigade when
277 the proxy loop is retried (ping), so I need to rework this.
278 Do you think we'd better remove the prefetch, or maybe just
279 make it nonblocking (by default)?
280 jim: Non-blocking seems the best way to handle...
282 PATCHES/ISSUES THAT ARE STALLED
284 * core: Add ap_errorlog_provider to make ErrorLog logging modular. This
285 backport keeps syslog logging as part of httpd core and only adds
286 API to allow other modules to be used for error logging.
287 trunk patch: http://svn.apache.org/r1525597
288 http://svn.apache.org/r1525664
289 http://svn.apache.org/r1525845
290 http://svn.apache.org/r1527003
291 http://svn.apache.org/r1527005
292 http://svn.apache.org/r1532344
293 http://svn.apache.org/r1539988
294 http://svn.apache.org/r1541029
295 http://svn.apache.org/r1543979
296 http://svn.apache.org/r1544156
297 http://svn.apache.org/r1626978
298 2.4.x patch: http://people.apache.org/~jkaluza/patches/httpd-2.4.x-errorlog_provider.patch
300 +1: covener w/ doc or code to fix syntax (providername:providerarg not supported like syslog or socacheproviders,
301 needs 2 args which is not valid in ErrorLog manual)
302 trawick: nit: fix "writing" in "/* NULL if we are writting to syslog */"
303 (sorry, haven't finished reviewing completely)
304 jim: What is the status of this??
306 * mod_proxy: Add ap_proxy_define_match_worker() and use it for ProxyPassMatch
307 and ProxyMatch section to distinguish between normal workers and workers
308 with regex substitutions in the name. Implement handling of such workers
309 in ap_proxy_get_worker(). Fixes the bug when regex workers were not
310 matched and used for request. PR 43513.
311 trunk patch: http://svn.apache.org/r1609680
312 http://svn.apache.org/r1609688
313 http://svn.apache.org/r1641381
314 ylavic: Merge patch provided (reusing new->real to avoid double de_socketfy() call).
315 Also added missing r1609688 to the patchset.
316 2.4.x patch: http://people.apache.org/~ylavic/httpd-2.4.x-ap_proxy_define_match_worker.patch
318 -0: covener tried to review this one in Austin with Jeff. Does the added match function
319 really cover a very narrow set of parameters with the way it skips over backreferences?
320 Also, why a new API vs. just setting the field inline?
322 * mod_systemd: New module, for integration with systemd on Linux.
323 trunk patch: http://svn.apache.org/r1393976
324 http://svn.apache.org/r1393997
325 http://svn.apache.org/r1484554
326 http://svn.apache.org/r1528032
327 http://svn.apache.org/r1528034
328 http://svn.apache.org/r1614821
329 http://svn.apache.org/r1618579
330 http://svn.apache.org/r1618588
331 2.4.x patch: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-mod_systemd.patch
334 * mod_journald: Add new module mod_journald to log error logs into journald.
335 This patch needs changes done in mod_systemd patch (already
337 trunk patch: http://svn.apache.org/r1610339
338 http://svn.apache.org/r1621806
339 2.4.x patch: http://people.apache.org/~jkaluza/patches/httpd-2.4.x-mod_journald.patch
341 rjung, minfrin: Not understanding "This patch needs changes done in
342 mod_systemd patch", am I right in understanding this patch is
344 jkaluza: No, that patch is not committed yet. It is in STALLED section.
345 The link for that patch is: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-mod_systemd.patch
347 * core: Add support for systemd socket activation.
348 trunk patch: http://svn.apache.org/r1511033
349 http://svn.apache.org/r1608686
350 http://svn.apache.org/r1608694
351 http://svn.apache.org/r1608703
352 http://svn.apache.org/r1608721
353 http://svn.apache.org/r1608744
354 2.4.x patch: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-socket-activation.patch
357 * mod_proxy: Ensure network errors detected by the proxy are returned as
358 504 Gateway Timout as opposed to 502 Bad Gateway
359 trunk patch: https://svn.apache.org/viewvc?view=revision&revision=1480058
360 2.4.x patch: trunk patch works modulo CHANGES
362 -1: rpluem: This change is still disputed. See
363 http://mail-archives.apache.org/mod_mbox/httpd-dev/201305.mbox/%3C1B16B9E3-87BA-4EEF-939C-7C7313B54714%40gbiv.com%3E
365 * cross-compile: allow to provide CC_FOR_BUILD so that gen_test_char will be
366 compiled by the build compiler instead of the host compiler.
367 Also set CC_FOR_BUILD to 'cc' when cross-compilation is detected.
368 Trunk patches: http://svn.apache.org/viewvc?view=revision&revision=1327907
369 http://svn.apache.org/viewvc?view=revision&revision=1328390
370 http://svn.apache.org/viewvc?view=revision&revision=1328714
371 2.4 patch: http://people.apache.org/~fuankg/diffs/httpd-2.4.x-cross_compile.diff
372 fuankg: on hold until we agree for a better and more simple solution ...
374 * Makefile.win: Added copying of .vbs / .wsf CGIs to Windows install target.
375 Moved fixing of shebang to separate target so that it is
376 no longer executed by default and all CGIs remain inactive.
377 trunk patch: http://svn.apache.org/viewvc?view=revision&revision=1387984
378 http://svn.apache.org/viewvc?view=revision&revision=1421203
379 http://svn.apache.org/viewvc?view=revision&revision=1421591
380 2.4.x patch: http://people.apache.org/~fuankg/diffs/httpd-2.4.x-Makefile.win.diff
383 This commit is essentially deciding that an httpd install on
384 Windows now has printenv/testcgi written in 2 more languages.
385 To the extent that the usefulness is that it shows how to make scripts
386 of these types executable by httpd, I believe that the documentation
387 is the proper place to solve that. To the extent that the usefullness
388 is to show how to implement a CGI in these particular languages, I believe
389 that the httpd distribution and documentation in general is not the
390 place for that. Historically these types of scripts have caused problems
391 for downstream vendorsas well as newbies (and sometimes the intersection
392 of those two groups) who don't understand that these are information leaks
393 once they are enabled, and the subtlety of the way they are disabled ("Apache
394 messed up the first line; let me fix that") contributes to that.
395 fuankg notes: I've just added a big warning to all CGI scripts which should now
396 make absolutely clear that these CGIs are for testing purpose only - so those
397 who enable those scripts with inserting the right shebang should be 100% aware
398 of any risks (this should cover your last point).
399 jim: trawick, does the above address your concerns?
400 trawick: to some extent (somebody reading the script gets an idea)
401 Why isn't the configuration requirement documented instead
402 of described indirectly in a sample?
403 Why are these new samples added to the install without three
404 votes? (I didn't veto it; put your name next to the two
405 existing ones and I'll be satisified that enough people
406 considered this addition as an appropriate solution for a
407 real httpd usability problem.)
408 wrowe: I'd agree with trawick, and suggest that these scripts can begin
409 their life somewhere in the manual/ tree. This really seems like
410 the place where /usr/share/httpd/examples/ would be useful, but
411 there isn't an ordinary directory for that. Since we want none
412 of the scripts to function 'out of the box', what about a new
413 cgi-examples/ dir alongside cgi-bin/? Otherwise manual/cgi/examples