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. ]
115 *) core: Prevent a server crash in case of an invalid CONNECT request with
116 a custom error page for status code 400 that uses server side includes.
118 Trunk version of patch:
119 http://svn.apache.org/r1727544
120 Backport version for 2.4.x of patch:
121 Trunk version of patch works modulo CHANGES
122 +1: rpluem, covener, ylavic
124 *) core: Add expression support to SetHandler (someone wanted this in
125 a well-articulated serverfault post).
126 trunk patch: http://svn.apache.org/r1725149
127 http://svn.apache.org/r1725151
128 http://svn.apache.org/r1726233
129 http://svn.apache.org/r1729374
130 2.4.x patch: MMN/changes only: http://people.apache.org/~covener/patches/2.4.x-sethandler-expr-2.diff
131 + http://svn.apache.org/r1729374
132 +1: covener, jim, ylavic
134 *) core: introducing new hook "pre_close_connection" to give protocols other
135 than http/1.1 a chance to send one last frame before close.
137 trunk patch: http://svn.apache.org/r1727071
138 http://svn.apache.org/r1727573
139 2.4.x patch: trunk works (modulo CHANGES)
140 +1: icing, covener, ylavic
141 covener: needs MMN bump, but sorting out previous MMN question first.
144 PATCHES PROPOSED TO BACKPORT FROM TRUNK:
145 [ New proposals should be added at the end of the list ]
147 *) mod_alias: Introduce expression parser support for Alias, ScriptAlias
148 and Redirect. Limit Redirect expressions to directory (Location) context
149 and redirect statuses (implicit or explicit).
150 trunk patch: http://svn.apache.org/r1653941
151 http://svn.apache.org/r1653978
152 http://svn.apache.org/r1656225
153 http://svn.apache.org/r1686853
154 http://svn.apache.org/r1686856
155 2.4.x patch: https://people.apache.org/~minfrin/httpd-mod_alias-expr2.patch
158 * core: Fix crash in ap_mpm_pod_check call caused by NULL dereference of
159 its parameter when starting httpd as single process (httpd -X).
160 trunk patch: http://svn.apache.org/r1711479
161 2.4.x patch: trunk works
163 minfrin: Needs extra parens to suppress a warning:
164 prefork.c:1319:16: note: place parentheses around the assignment
165 to silence this warning
166 jailletc36: This has been done in r1711919
167 ylavic: Also, I don't think the changes on worker/event are needed,
168 only prefork requires the accept mutex in ONE_PROCESS mode.
170 *) mod_ssl: Free dhparams when getting DH params. This fixes issue when
171 SSLCryptoDevice does not get unregistered because of non-zero refcount
172 during the mod_ssl unload happening on httpd startup.
173 trunk patch: http://svn.apache.org/r1720129
174 2.4.x patch: http://jkaluza.fedorapeople.org/httpd-2.4.x-dhparams-free.patch
176 ylavic: +1 with r1723295 (likewise for ecparams).
178 *) mod_cache_socache: Fix a possible cached entity body corruption when it
179 is received from an origin server in multiple batches and forwarded by
181 trunk patch: http://svn.apache.org/r1721899
182 2.4.x patch: trunk works, module CHANGES
185 *) mod_ssl: Add SSLOCSPProxyURL to add the possibility to do all queries
186 to OCSP responders through a HTTP proxy.
187 Trunk version of patch:
188 http://svn.apache.org/r1726881
189 http://svn.apache.org/r1727111
190 Backport version for 2.4.x of patch:
191 Trunk version of patch works modulo CHANGES
194 *) mod_proxy_hcheck: Dynamic reverse proxy backend health check module
195 Trunk version of patch:
196 Backport version for 2.4.x of patch:
199 *) mod_remoteip: Prevent an external proxy from presenting an internal proxy
201 Trunk version of patch:
202 http://svn.apache.org/r1588330
203 Trunk patch applies clean, modulo CHANGES
206 PATCHES/ISSUES THAT ARE BEING WORKED
208 *) http: Don't remove the Content-Length of zero from a HEAD response if
209 it comes from an origin server, module or script. Allow the previous
210 behaviour (for legacy/buggy modules only, not origin) by also backporting
211 the HttpContentLengthHeadZero directive (and also HttpExpectStrict which
212 comes for free with the same commit).
213 trunk patch: http://svn.apache.org/r1554303
214 http://svn.apache.org/r1678215
215 2.4.x patch: http://people.apache.org/~ylavic/httpd-2.4.x-preserve_head_cl_zero.patch
217 ylavic: r1554303 issued a major MMN bump, but since the ABI change is two
218 ints added at the end of core_server_config, the proposed merge
219 does a minor bump only.
220 minfrin: Two new directives need to be documented.
222 * mod_proxy_http: Don't establish or reuse a backend connection before pre-
223 fetching the request body, so to minimize the delay between it is supposed
224 to be alive and the first bytes sent: this is a best effort to prevent the
225 backend from closing because of idle or keepalive timeout in the meantime.
226 Also, handle a new "proxy-flushall" environment variable which allows to
227 flush any forwarded body data immediately. PR 56541+37920.
228 trunk patch: http://svn.apache.org/r1656259
229 http://svn.apache.org/r1656359 (CHANGES entry)
230 2.4.x patch: trunk works (modulo CHANGES, docs/log-message-tags)
232 -0: jim: This seems to be a hit to normal performance, to handle an
233 error and/or non-normal condition. The pre-fetch is
234 expensive, and is always done, even before we know that
235 the backend is available to rec' it. I understand the
236 error described, but is the fix actually worth it (plus
237 it seems to allow for a DDoS vector).
238 ylavic: It seems to me that the problem is real since we reuse the
239 connection before prefetching 16K (either controlled by the
240 client, or by an input filter), we currently always prefetch
241 these bytes already. Regarding performance I don't see any
242 difference (more cycles) compared with the current code.
243 However I think I failed to rebuild the header_brigade when
244 the proxy loop is retried (ping), so I need to rework this.
245 Do you think we'd better remove the prefetch, or maybe just
246 make it nonblocking (by default)?
247 jim: Non-blocking seems the best way to handle...
249 PATCHES/ISSUES THAT ARE STALLED
251 * core: Add ap_errorlog_provider to make ErrorLog logging modular. This
252 backport keeps syslog logging as part of httpd core and only adds
253 API to allow other modules to be used for error logging.
254 trunk patch: http://svn.apache.org/r1525597
255 http://svn.apache.org/r1525664
256 http://svn.apache.org/r1525845
257 http://svn.apache.org/r1527003
258 http://svn.apache.org/r1527005
259 http://svn.apache.org/r1532344
260 http://svn.apache.org/r1539988
261 http://svn.apache.org/r1541029
262 http://svn.apache.org/r1543979
263 http://svn.apache.org/r1544156
264 http://svn.apache.org/r1626978
265 2.4.x patch: http://people.apache.org/~jkaluza/patches/httpd-2.4.x-errorlog_provider.patch
267 +1: covener w/ doc or code to fix syntax (providername:providerarg not supported like syslog or socacheproviders,
268 needs 2 args which is not valid in ErrorLog manual)
269 trawick: nit: fix "writing" in "/* NULL if we are writting to syslog */"
270 (sorry, haven't finished reviewing completely)
271 jim: What is the status of this??
273 * mod_proxy: Add ap_proxy_define_match_worker() and use it for ProxyPassMatch
274 and ProxyMatch section to distinguish between normal workers and workers
275 with regex substitutions in the name. Implement handling of such workers
276 in ap_proxy_get_worker(). Fixes the bug when regex workers were not
277 matched and used for request. PR 43513.
278 trunk patch: http://svn.apache.org/r1609680
279 http://svn.apache.org/r1609688
280 http://svn.apache.org/r1641381
281 ylavic: Merge patch provided (reusing new->real to avoid double de_socketfy() call).
282 Also added missing r1609688 to the patchset.
283 2.4.x patch: http://people.apache.org/~ylavic/httpd-2.4.x-ap_proxy_define_match_worker.patch
285 -0: covener tried to review this one in Austin with Jeff. Does the added match function
286 really cover a very narrow set of parameters with the way it skips over backreferences?
287 Also, why a new API vs. just setting the field inline?
289 * mod_systemd: New module, for integration with systemd on Linux.
290 trunk patch: http://svn.apache.org/r1393976
291 http://svn.apache.org/r1393997
292 http://svn.apache.org/r1484554
293 http://svn.apache.org/r1528032
294 http://svn.apache.org/r1528034
295 http://svn.apache.org/r1614821
296 http://svn.apache.org/r1618579
297 http://svn.apache.org/r1618588
298 2.4.x patch: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-mod_systemd.patch
301 * mod_journald: Add new module mod_journald to log error logs into journald.
302 This patch needs changes done in mod_systemd patch (already
304 trunk patch: http://svn.apache.org/r1610339
305 http://svn.apache.org/r1621806
306 2.4.x patch: http://people.apache.org/~jkaluza/patches/httpd-2.4.x-mod_journald.patch
308 rjung, minfrin: Not understanding "This patch needs changes done in
309 mod_systemd patch", am I right in understanding this patch is
311 jkaluza: No, that patch is not committed yet. It is in STALLED section.
312 The link for that patch is: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-mod_systemd.patch
314 * core: Add support for systemd socket activation.
315 trunk patch: http://svn.apache.org/r1511033
316 http://svn.apache.org/r1608686
317 http://svn.apache.org/r1608694
318 http://svn.apache.org/r1608703
319 http://svn.apache.org/r1608721
320 http://svn.apache.org/r1608744
321 2.4.x patch: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-socket-activation.patch
324 * mod_proxy: Ensure network errors detected by the proxy are returned as
325 504 Gateway Timout as opposed to 502 Bad Gateway
326 trunk patch: https://svn.apache.org/viewvc?view=revision&revision=1480058
327 2.4.x patch: trunk patch works modulo CHANGES
329 -1: rpluem: This change is still disputed. See
330 http://mail-archives.apache.org/mod_mbox/httpd-dev/201305.mbox/%3C1B16B9E3-87BA-4EEF-939C-7C7313B54714%40gbiv.com%3E
332 * cross-compile: allow to provide CC_FOR_BUILD so that gen_test_char will be
333 compiled by the build compiler instead of the host compiler.
334 Also set CC_FOR_BUILD to 'cc' when cross-compilation is detected.
335 Trunk patches: http://svn.apache.org/viewvc?view=revision&revision=1327907
336 http://svn.apache.org/viewvc?view=revision&revision=1328390
337 http://svn.apache.org/viewvc?view=revision&revision=1328714
338 2.4 patch: http://people.apache.org/~fuankg/diffs/httpd-2.4.x-cross_compile.diff
339 fuankg: on hold until we agree for a better and more simple solution ...
341 * Makefile.win: Added copying of .vbs / .wsf CGIs to Windows install target.
342 Moved fixing of shebang to separate target so that it is
343 no longer executed by default and all CGIs remain inactive.
344 trunk patch: http://svn.apache.org/viewvc?view=revision&revision=1387984
345 http://svn.apache.org/viewvc?view=revision&revision=1421203
346 http://svn.apache.org/viewvc?view=revision&revision=1421591
347 2.4.x patch: http://people.apache.org/~fuankg/diffs/httpd-2.4.x-Makefile.win.diff
350 This commit is essentially deciding that an httpd install on
351 Windows now has printenv/testcgi written in 2 more languages.
352 To the extent that the usefulness is that it shows how to make scripts
353 of these types executable by httpd, I believe that the documentation
354 is the proper place to solve that. To the extent that the usefullness
355 is to show how to implement a CGI in these particular languages, I believe
356 that the httpd distribution and documentation in general is not the
357 place for that. Historically these types of scripts have caused problems
358 for downstream vendorsas well as newbies (and sometimes the intersection
359 of those two groups) who don't understand that these are information leaks
360 once they are enabled, and the subtlety of the way they are disabled ("Apache
361 messed up the first line; let me fix that") contributes to that.
362 fuankg notes: I've just added a big warning to all CGI scripts which should now
363 make absolutely clear that these CGIs are for testing purpose only - so those
364 who enable those scripts with inserting the right shebang should be 100% aware
365 of any risks (this should cover your last point).
366 jim: trawick, does the above address your concerns?
367 trawick: to some extent (somebody reading the script gets an idea)
368 Why isn't the configuration requirement documented instead
369 of described indirectly in a sample?
370 Why are these new samples added to the install without three
371 votes? (I didn't veto it; put your name next to the two
372 existing ones and I'll be satisified that enough people
373 considered this addition as an appropriate solution for a
374 real httpd usability problem.)
375 wrowe: I'd agree with trawick, and suggest that these scripts can begin
376 their life somewhere in the manual/ tree. This really seems like
377 the place where /usr/share/httpd/examples/ would be useful, but
378 there isn't an ordinary directory for that. Since we want none
379 of the scripts to function 'out of the box', what about a new
380 cgi-examples/ dir alongside cgi-bin/? Otherwise manual/cgi/examples