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 December 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. ]
115 *) core: Add missing APLOGNO() from r1729495 (somehow r1725395 was
116 backported in r1729495 but without this "server/core.c" change)
117 trunk patch: http://svn.apache.org/viewvc/httpd/httpd/trunk/server/core.c?r1=1725395&r2=1725394&pathrev=1725395&view=patch
118 2.4.x patch: trunk above works
119 +1: ylavic, icing, jim
123 PATCHES PROPOSED TO BACKPORT FROM TRUNK:
124 [ New proposals should be added at the end of the list ]
126 *) mod_ssl: Free dhparams when getting DH params. This fixes issue when
127 SSLCryptoDevice does not get unregistered because of non-zero refcount
128 during the mod_ssl unload happening on httpd startup.
129 trunk patch: http://svn.apache.org/r1720129
130 http://svn.apache.org/r1723295
131 http://svn.apache.org/r1733088
132 http://svn.apache.org/r1733089
133 2.4.x patch: http://home.apache.org/~ylavic/patches/httpd-2.4.x-dh_leaks.patch
135 rpluem says: Can we get an updated 2.4.x proposal that includes r1723295?
136 ylavic: done + CHANGES (votes reset)
138 *) mod_proxy_hcheck: Dynamic reverse proxy backend health check module
139 Trunk version of patch: <various>
140 Backport version for 2.4.x of patch:
141 http://home.apache.org/~jim/patches/hcheck-2.4-v2.patch
144 ylavic: Looks like the changes on struct proxy_worker_shared would break
145 startup with "BalancerPersist on" due to the strict checks on
146 the sizes of existing slotmems (slotmem_create/attach)?
147 jim: Yes, that is right (re: breakage)... this would be noted at
150 *) Use pre_connection hook in event.c to properly setup connection state
151 of slave connections (eliminates hacks in mod_http2).
153 http://svn.apache.org/r1727603
155 Trunk version of patch works modulo CHANGES
158 *) mod_proxy: Play/restore the TLS-SNI on new backend connections which
159 had to be issued because the remote closed the previous/reusable one
160 during idle (keep-alive) time.
161 trunk patch: http://svn.apache.org/r1729826
162 http://svn.apache.org/r1729847
163 http://svn.apache.org/r1732986
164 http://svn.apache.org/r1733056
165 2.4.x patch: http://home.apache.org/~ylavic/patches/httpd-2.4.x-mod_proxy-SNI_reuse-v2.patch
168 * prefork: Fix crash in ap_mpm_pod_check call caused by NULL dereference of
169 its parameter when starting httpd as single process (httpd -X).
170 trunk patch: http://svn.apache.org/r1711479
171 http://svn.apache.org/r1733064
172 http://svn.apache.org/r1733068
173 2.4.x patch: http://home.apache.org/~ylavic/patches/httpd-2.4.x-prefork-ONE_PROCESS_POD.patch
176 *) mod_ssl: When SSLVerify is disabled (NONE), don't force a renegotiation if
177 the SSLVerifyDepth applied with the default/handshaken vhost differs from
178 the one applicable with the finally selected vhost.
179 trunk patch: http://svn.apache.org/r1684171
180 2.4.x patch: http://home.apache.org/~ylavic/patches/httpd-2.4.x-SSLVerify_NONE_no_reneg_Depth.patch
183 *) core: Ensure that httpd exits with an error status when the MPM fails
185 trunk patch: http://svn.apache.org/r1629925
186 http://svn.apache.org/r1629927
187 http://svn.apache.org/r1629928
188 http://svn.apache.org/r1733162
189 http://svn.apache.org/r1733173
190 2.4.x patch: http://home.apache.org/~ylavic/patches/httpd-2.4.x-exit_with_error_on_mpm_failure.patch
194 PATCHES/ISSUES THAT ARE BEING WORKED
196 *) http: Don't remove the Content-Length of zero from a HEAD response if
197 it comes from an origin server, module or script. Allow the previous
198 behaviour (for legacy/buggy modules only, not origin) by also backporting
199 the HttpContentLengthHeadZero directive (and also HttpExpectStrict which
200 comes for free with the same commit).
201 trunk patch: http://svn.apache.org/r1554303
202 http://svn.apache.org/r1678215
203 2.4.x patch: http://people.apache.org/~ylavic/httpd-2.4.x-preserve_head_cl_zero.patch
205 ylavic: r1554303 issued a major MMN bump, but since the ABI change is two
206 ints added at the end of core_server_config, the proposed merge
207 does a minor bump only.
208 minfrin: Two new directives need to be documented.
210 * mod_proxy_http: Don't establish or reuse a backend connection before pre-
211 fetching the request body, so to minimize the delay between it is supposed
212 to be alive and the first bytes sent: this is a best effort to prevent the
213 backend from closing because of idle or keepalive timeout in the meantime.
214 Also, handle a new "proxy-flushall" environment variable which allows to
215 flush any forwarded body data immediately. PR 56541+37920.
216 trunk patch: http://svn.apache.org/r1656259
217 http://svn.apache.org/r1656359 (CHANGES entry)
218 2.4.x patch: trunk works (modulo CHANGES, docs/log-message-tags)
220 -0: jim: This seems to be a hit to normal performance, to handle an
221 error and/or non-normal condition. The pre-fetch is
222 expensive, and is always done, even before we know that
223 the backend is available to rec' it. I understand the
224 error described, but is the fix actually worth it (plus
225 it seems to allow for a DDoS vector).
226 ylavic: It seems to me that the problem is real since we reuse the
227 connection before prefetching 16K (either controlled by the
228 client, or by an input filter), we currently always prefetch
229 these bytes already. Regarding performance I don't see any
230 difference (more cycles) compared with the current code.
231 However I think I failed to rebuild the header_brigade when
232 the proxy loop is retried (ping), so I need to rework this.
233 Do you think we'd better remove the prefetch, or maybe just
234 make it nonblocking (by default)?
235 jim: Non-blocking seems the best way to handle...
237 PATCHES/ISSUES THAT ARE STALLED
239 * core: Add ap_errorlog_provider to make ErrorLog logging modular. This
240 backport keeps syslog logging as part of httpd core and only adds
241 API to allow other modules to be used for error logging.
242 trunk patch: http://svn.apache.org/r1525597
243 http://svn.apache.org/r1525664
244 http://svn.apache.org/r1525845
245 http://svn.apache.org/r1527003
246 http://svn.apache.org/r1527005
247 http://svn.apache.org/r1532344
248 http://svn.apache.org/r1539988
249 http://svn.apache.org/r1541029
250 http://svn.apache.org/r1543979
251 http://svn.apache.org/r1544156
252 http://svn.apache.org/r1626978
253 2.4.x patch: http://people.apache.org/~jkaluza/patches/httpd-2.4.x-errorlog_provider.patch
255 +1: covener w/ doc or code to fix syntax (providername:providerarg not supported like syslog or socacheproviders,
256 needs 2 args which is not valid in ErrorLog manual)
257 trawick: nit: fix "writing" in "/* NULL if we are writting to syslog */"
258 (sorry, haven't finished reviewing completely)
259 jim: What is the status of this??
261 * mod_proxy: Add ap_proxy_define_match_worker() and use it for ProxyPassMatch
262 and ProxyMatch section to distinguish between normal workers and workers
263 with regex substitutions in the name. Implement handling of such workers
264 in ap_proxy_get_worker(). Fixes the bug when regex workers were not
265 matched and used for request. PR 43513.
266 trunk patch: http://svn.apache.org/r1609680
267 http://svn.apache.org/r1609688
268 http://svn.apache.org/r1641381
269 ylavic: Merge patch provided (reusing new->real to avoid double de_socketfy() call).
270 Also added missing r1609688 to the patchset.
271 2.4.x patch: http://people.apache.org/~ylavic/httpd-2.4.x-ap_proxy_define_match_worker.patch
273 -0: covener tried to review this one in Austin with Jeff. Does the added match function
274 really cover a very narrow set of parameters with the way it skips over backreferences?
275 Also, why a new API vs. just setting the field inline?
277 * mod_systemd: New module, for integration with systemd on Linux.
278 trunk patch: http://svn.apache.org/r1393976
279 http://svn.apache.org/r1393997
280 http://svn.apache.org/r1484554
281 http://svn.apache.org/r1528032
282 http://svn.apache.org/r1528034
283 http://svn.apache.org/r1614821
284 http://svn.apache.org/r1618579
285 http://svn.apache.org/r1618588
286 2.4.x patch: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-mod_systemd.patch
288 sf comments: The IdleShutdown logic seems broken. Consider a single
289 active connection that is stalled for 10 seconds. That
290 connection will be broken after GracefulShutdownTimeout.
291 A better logic would be to check if there is any open
292 connection that is not in keep-alive state.
294 * mod_journald: Add new module mod_journald to log error logs into journald.
295 This patch needs changes done in mod_systemd patch (already
297 trunk patch: http://svn.apache.org/r1610339
298 http://svn.apache.org/r1621806
299 2.4.x patch: http://people.apache.org/~jkaluza/patches/httpd-2.4.x-mod_journald.patch
301 rjung, minfrin: Not understanding "This patch needs changes done in
302 mod_systemd patch", am I right in understanding this patch is
304 jkaluza: No, that patch is not committed yet. It is in STALLED section.
305 The link for that patch is: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-mod_systemd.patch
307 * core: Add support for systemd socket activation.
308 trunk patch: http://svn.apache.org/r1511033
309 http://svn.apache.org/r1608686
310 http://svn.apache.org/r1608694
311 http://svn.apache.org/r1608703
312 http://svn.apache.org/r1608721
313 http://svn.apache.org/r1608744
314 2.4.x patch: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-socket-activation.patch
317 * mod_proxy: Ensure network errors detected by the proxy are returned as
318 504 Gateway Timout as opposed to 502 Bad Gateway
319 trunk patch: https://svn.apache.org/viewvc?view=revision&revision=1480058
320 2.4.x patch: trunk patch works modulo CHANGES
322 -1: rpluem: This change is still disputed. See
323 http://mail-archives.apache.org/mod_mbox/httpd-dev/201305.mbox/%3C1B16B9E3-87BA-4EEF-939C-7C7313B54714%40gbiv.com%3E
325 * cross-compile: allow to provide CC_FOR_BUILD so that gen_test_char will be
326 compiled by the build compiler instead of the host compiler.
327 Also set CC_FOR_BUILD to 'cc' when cross-compilation is detected.
328 Trunk patches: http://svn.apache.org/viewvc?view=revision&revision=1327907
329 http://svn.apache.org/viewvc?view=revision&revision=1328390
330 http://svn.apache.org/viewvc?view=revision&revision=1328714
331 2.4 patch: http://people.apache.org/~fuankg/diffs/httpd-2.4.x-cross_compile.diff
332 fuankg: on hold until we agree for a better and more simple solution ...
334 * Makefile.win: Added copying of .vbs / .wsf CGIs to Windows install target.
335 Moved fixing of shebang to separate target so that it is
336 no longer executed by default and all CGIs remain inactive.
337 trunk patch: http://svn.apache.org/viewvc?view=revision&revision=1387984
338 http://svn.apache.org/viewvc?view=revision&revision=1421203
339 http://svn.apache.org/viewvc?view=revision&revision=1421591
340 2.4.x patch: http://people.apache.org/~fuankg/diffs/httpd-2.4.x-Makefile.win.diff
343 This commit is essentially deciding that an httpd install on
344 Windows now has printenv/testcgi written in 2 more languages.
345 To the extent that the usefulness is that it shows how to make scripts
346 of these types executable by httpd, I believe that the documentation
347 is the proper place to solve that. To the extent that the usefullness
348 is to show how to implement a CGI in these particular languages, I believe
349 that the httpd distribution and documentation in general is not the
350 place for that. Historically these types of scripts have caused problems
351 for downstream vendorsas well as newbies (and sometimes the intersection
352 of those two groups) who don't understand that these are information leaks
353 once they are enabled, and the subtlety of the way they are disabled ("Apache
354 messed up the first line; let me fix that") contributes to that.
355 fuankg notes: I've just added a big warning to all CGI scripts which should now
356 make absolutely clear that these CGIs are for testing purpose only - so those
357 who enable those scripts with inserting the right shebang should be 100% aware
358 of any risks (this should cover your last point).
359 jim: trawick, does the above address your concerns?
360 trawick: to some extent (somebody reading the script gets an idea)
361 Why isn't the configuration requirement documented instead
362 of described indirectly in a sample?
363 Why are these new samples added to the install without three
364 votes? (I didn't veto it; put your name next to the two
365 existing ones and I'll be satisified that enough people
366 considered this addition as an appropriate solution for a
367 real httpd usability problem.)
368 wrowe: I'd agree with trawick, and suggest that these scripts can begin
369 their life somewhere in the manual/ tree. This really seems like
370 the place where /usr/share/httpd/examples/ would be useful, but
371 there isn't an ordinary directory for that. Since we want none
372 of the scripts to function 'out of the box', what about a new
373 cgi-examples/ dir alongside cgi-bin/? Otherwise manual/cgi/examples