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