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. ]
116 *) mod_ssl: Fix some duplicate definitions
117 trunk patch: http://svn.apache.org/r1726888
118 2.4.x patch: trunk works
119 +1: mrumph, icing, jim
121 PATCHES PROPOSED TO BACKPORT FROM TRUNK:
122 [ New proposals should be added at the end of the list ]
124 *) mod_alias: Introduce expression parser support for Alias, ScriptAlias
125 and Redirect. Limit Redirect expressions to directory (Location) context
126 and redirect statuses (implicit or explicit).
127 trunk patch: http://svn.apache.org/r1653941
128 http://svn.apache.org/r1653978
129 http://svn.apache.org/r1656225
130 http://svn.apache.org/r1686853
131 http://svn.apache.org/r1686856
132 2.4.x patch: https://people.apache.org/~minfrin/httpd-mod_alias-expr2.patch
135 * core: Fix crash in ap_mpm_pod_check call caused by NULL dereference of
136 its parameter when starting httpd as single process (httpd -X).
137 trunk patch: http://svn.apache.org/r1711479
138 2.4.x patch: trunk works
140 minfrin: Needs extra parens to suppress a warning:
141 prefork.c:1319:16: note: place parentheses around the assignment
142 to silence this warning
143 jailletc36: This has been done in r1711919
144 ylavic: Also, I don't think the changes on worker/event are needed,
145 prefork only requires the accept mutex in ONE_PROCESS mode.
147 *) mod_ssl: Fix missing TLS Upgrade/Connection headers on OPTIONS * requests
148 (Note that this is simply a necessary band-aid, and still won't allow h2c
149 to peacefully coexist with tls/n.n upgrades, because Upgrade phase needs
150 to come earlier, not as a handler, and the bogus connection-close behavior
151 must be removed before the Protocol API can handle TLS upgrade.)
153 trunk patch: http://svn.apache.org/r1717816
155 ylavic: how about adding !ap_request_has_body(r) to the test then?
156 wrowe responds: nonstarter, as discussed on list.
158 *) mod_ssl: Free dhparams when getting DH params. This fixes issue when
159 SSLCryptoDevice does not get unregistered because of non-zero refcount
160 during the mod_ssl unload happening on httpd startup.
161 trunk patch: http://svn.apache.org/r1720129
162 2.4.x patch: http://jkaluza.fedorapeople.org/httpd-2.4.x-dhparams-free.patch
165 *) mod_cache_socache: Fix a possible cached entity body corruption when it
166 is received from an origin server in multiple batches and forwarded by
168 trunk patch: http://svn.apache.org/r1721899
169 2.4.x patch: trunk works, module CHANGES
172 *) core: Add expression support to SetHandler (someone wanted this in
173 a well-articulated serverfault post).
174 trunk patch: http://svn.apache.org/r1725149
175 http://svn.apache.org/r1725151
176 http://svn.apache.org/r1726233
177 2.4.x patch: MMN/changes only: http://people.apache.org/~covener/patches/2.4.x-sethandler-expr-2.diff
180 *) Add APLOGNO, first chunk (those that were detected by coccinelle).
181 There are some more but they are easier to backport once these here are applied.
182 trunk patch: http://svn.apache.org/r1725392 (modules)
183 http://svn.apache.org/r1725394 (server/mpm)
184 http://svn.apache.org/r1725395 (server others)
185 http://svn.apache.org/r1725468 (remove APLOGNO from mod_log_debug custom messages)
186 2.4.x patch: http://people.apache.org/~rjung/patches/aplogno-backport-r1725392.patch
187 http://people.apache.org/~rjung/patches/aplogno-backport-r1725394.patch
188 http://people.apache.org/~rjung/patches/aplogno-backport-r1725395.patch
189 http://people.apache.org/~rjung/patches/aplogno-backport-r1725468.patch
191 icing: needs http://svn.apache.org/r1725468
192 rjung: You are right, I added r1725468 and restart the vote.
193 @Jim: Only r1725468 is new: removing the added APLOGNO from
194 mod_log_debug where we actually log the configured custom
195 log messages. Admins can provide their own LOGNO as part
196 of the ocnfigured log message. It doesn't make sense to
199 *) mod_ssl: handle APR_TIMEUP on empty input by keeping connection state valid
201 trunk patch: http://svn.apache.org/r1725940
204 *) When more than one module calls APACHE_CHECK_OPENSSL, MOD_LDFLAGS and MOD_CFLAGS
205 remain unset for second or later caller. Fix this by caching the values for
206 MOD_LDFLAGS and MOD_CFLAGS created during the first run and set them in the
207 cached case. Change by rpluem
208 trunk patch: http://svn.apache.org/r1725325
209 2.4.x patch: trunk works
212 *) core: introducing new hook "pre_close_connection" to give protocols other
213 than http/1.1 a chance to send one last frame before close.
215 trunk patch: http://svn.apache.org/r1727071
216 http://svn.apache.org/r1727573
217 2.4.x patch: trunk works (modulo CHANGES)
220 *) core: Prevent a server crash in case of an invalid CONNECT request with
221 a custom error page for status code 400 that uses server side includes.
223 Trunk version of patch:
224 http://svn.apache.org/r1727544
225 Backport version for 2.4.x of patch:
226 Trunk version of patch works modulo CHANGES
229 *) mod_ssl: Add SSLOCSPProxyURL to add the possibility to do all queries
230 to OCSP responders through a HTTP proxy.
231 Trunk version of patch:
232 http://svn.apache.org/r1726881
233 http://svn.apache.org/r1727111
234 Backport version for 2.4.x of patch:
235 Trunk version of patch works modulo CHANGES
238 *) mod_proxy_hcheck: Dynamic reverse proxy backend health check module
239 Trunk version of patch:
240 Backport version for 2.4.x of patch:
243 PATCHES/ISSUES THAT ARE BEING WORKED
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 PATCHES/ISSUES THAT ARE STALLED
288 * core: Add ap_errorlog_provider to make ErrorLog logging modular. This
289 backport keeps syslog logging as part of httpd core and only adds
290 API to allow other modules to be used for error logging.
291 trunk patch: http://svn.apache.org/r1525597
292 http://svn.apache.org/r1525664
293 http://svn.apache.org/r1525845
294 http://svn.apache.org/r1527003
295 http://svn.apache.org/r1527005
296 http://svn.apache.org/r1532344
297 http://svn.apache.org/r1539988
298 http://svn.apache.org/r1541029
299 http://svn.apache.org/r1543979
300 http://svn.apache.org/r1544156
301 http://svn.apache.org/r1626978
302 2.4.x patch: http://people.apache.org/~jkaluza/patches/httpd-2.4.x-errorlog_provider.patch
304 +1: covener w/ doc or code to fix syntax (providername:providerarg not supported like syslog or socacheproviders,
305 needs 2 args which is not valid in ErrorLog manual)
306 trawick: nit: fix "writing" in "/* NULL if we are writting to syslog */"
307 (sorry, haven't finished reviewing completely)
308 jim: What is the status of this??
310 * mod_proxy: Add ap_proxy_define_match_worker() and use it for ProxyPassMatch
311 and ProxyMatch section to distinguish between normal workers and workers
312 with regex substitutions in the name. Implement handling of such workers
313 in ap_proxy_get_worker(). Fixes the bug when regex workers were not
314 matched and used for request. PR 43513.
315 trunk patch: http://svn.apache.org/r1609680
316 http://svn.apache.org/r1609688
317 http://svn.apache.org/r1641381
318 ylavic: Merge patch provided (reusing new->real to avoid double de_socketfy() call).
319 Also added missing r1609688 to the patchset.
320 2.4.x patch: http://people.apache.org/~ylavic/httpd-2.4.x-ap_proxy_define_match_worker.patch
322 -0: covener tried to review this one in Austin with Jeff. Does the added match function
323 really cover a very narrow set of parameters with the way it skips over backreferences?
324 Also, why a new API vs. just setting the field inline?
326 * mod_systemd: New module, for integration with systemd on Linux.
327 trunk patch: http://svn.apache.org/r1393976
328 http://svn.apache.org/r1393997
329 http://svn.apache.org/r1484554
330 http://svn.apache.org/r1528032
331 http://svn.apache.org/r1528034
332 http://svn.apache.org/r1614821
333 http://svn.apache.org/r1618579
334 http://svn.apache.org/r1618588
335 2.4.x patch: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-mod_systemd.patch
338 * mod_journald: Add new module mod_journald to log error logs into journald.
339 This patch needs changes done in mod_systemd patch (already
341 trunk patch: http://svn.apache.org/r1610339
342 http://svn.apache.org/r1621806
343 2.4.x patch: http://people.apache.org/~jkaluza/patches/httpd-2.4.x-mod_journald.patch
345 rjung, minfrin: Not understanding "This patch needs changes done in
346 mod_systemd patch", am I right in understanding this patch is
348 jkaluza: No, that patch is not committed yet. It is in STALLED section.
349 The link for that patch is: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-mod_systemd.patch
351 * core: Add support for systemd socket activation.
352 trunk patch: http://svn.apache.org/r1511033
353 http://svn.apache.org/r1608686
354 http://svn.apache.org/r1608694
355 http://svn.apache.org/r1608703
356 http://svn.apache.org/r1608721
357 http://svn.apache.org/r1608744
358 2.4.x patch: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-socket-activation.patch
361 * mod_proxy: Ensure network errors detected by the proxy are returned as
362 504 Gateway Timout as opposed to 502 Bad Gateway
363 trunk patch: https://svn.apache.org/viewvc?view=revision&revision=1480058
364 2.4.x patch: trunk patch works modulo CHANGES
366 -1: rpluem: This change is still disputed. See
367 http://mail-archives.apache.org/mod_mbox/httpd-dev/201305.mbox/%3C1B16B9E3-87BA-4EEF-939C-7C7313B54714%40gbiv.com%3E
369 * cross-compile: allow to provide CC_FOR_BUILD so that gen_test_char will be
370 compiled by the build compiler instead of the host compiler.
371 Also set CC_FOR_BUILD to 'cc' when cross-compilation is detected.
372 Trunk patches: http://svn.apache.org/viewvc?view=revision&revision=1327907
373 http://svn.apache.org/viewvc?view=revision&revision=1328390
374 http://svn.apache.org/viewvc?view=revision&revision=1328714
375 2.4 patch: http://people.apache.org/~fuankg/diffs/httpd-2.4.x-cross_compile.diff
376 fuankg: on hold until we agree for a better and more simple solution ...
378 * Makefile.win: Added copying of .vbs / .wsf CGIs to Windows install target.
379 Moved fixing of shebang to separate target so that it is
380 no longer executed by default and all CGIs remain inactive.
381 trunk patch: http://svn.apache.org/viewvc?view=revision&revision=1387984
382 http://svn.apache.org/viewvc?view=revision&revision=1421203
383 http://svn.apache.org/viewvc?view=revision&revision=1421591
384 2.4.x patch: http://people.apache.org/~fuankg/diffs/httpd-2.4.x-Makefile.win.diff
387 This commit is essentially deciding that an httpd install on
388 Windows now has printenv/testcgi written in 2 more languages.
389 To the extent that the usefulness is that it shows how to make scripts
390 of these types executable by httpd, I believe that the documentation
391 is the proper place to solve that. To the extent that the usefullness
392 is to show how to implement a CGI in these particular languages, I believe
393 that the httpd distribution and documentation in general is not the
394 place for that. Historically these types of scripts have caused problems
395 for downstream vendorsas well as newbies (and sometimes the intersection
396 of those two groups) who don't understand that these are information leaks
397 once they are enabled, and the subtlety of the way they are disabled ("Apache
398 messed up the first line; let me fix that") contributes to that.
399 fuankg notes: I've just added a big warning to all CGI scripts which should now
400 make absolutely clear that these CGIs are for testing purpose only - so those
401 who enable those scripts with inserting the right shebang should be 100% aware
402 of any risks (this should cover your last point).
403 jim: trawick, does the above address your concerns?
404 trawick: to some extent (somebody reading the script gets an idea)
405 Why isn't the configuration requirement documented instead
406 of described indirectly in a sample?
407 Why are these new samples added to the install without three
408 votes? (I didn't veto it; put your name next to the two
409 existing ones and I'll be satisified that enough people
410 considered this addition as an appropriate solution for a
411 real httpd usability problem.)
412 wrowe: I'd agree with trawick, and suggest that these scripts can begin
413 their life somewhere in the manual/ tree. This really seems like
414 the place where /usr/share/httpd/examples/ would be useful, but
415 there isn't an ordinary directory for that. Since we want none
416 of the scripts to function 'out of the box', what about a new
417 cgi-examples/ dir alongside cgi-bin/? Otherwise manual/cgi/examples