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 *) mod_ssl: Constify + save a few bytes in conf pool when parsing SSLRequire
169 mod_nw_ssl: Save a few bytes in conf pool when processing 'NWSSLTrustedCerts'
170 trunk patch: http://svn.apache.org/r1718514
171 http://svn.apache.org/r1721313 (untested because I don't have this system)
172 2.4.x patch: trunk works
175 *) core: Save memory when calling 'ap_parse_htaccess'
176 trunk patch: http://svn.apache.org/r1719016
177 2.4.x patch: trunk works
178 +1: jailletc36, covener, jim
180 *) Use 'apr_pstrmemdup' instead of 'apr_pstrndup' when applicable in order
181 to save a few cycles.
182 Fix some style issues.
183 trunk patch: http://svn.apache.org/r1719018
184 http://svn.apache.org/r1719189
185 http://svn.apache.org/r1719190
186 2.4.x patch: trunk works
187 +1: jailletc36, covener, jim
189 *) mod_negotiation: Use 'ap_array_str_contains' to simplify code.
192 trunk patch: http://svn.apache.org/r1719252
193 http://svn.apache.org/r1719254
194 http://svn.apache.org/r1719255
195 http://svn.apache.org/r1720996 (change in ap_method_in_list not
196 tested, it is not actually used)
197 2.4.x patch: trunk works
198 +1: jailletc36, covener, jim
200 *) mod_mod_authn_socache: Do not use the magic string "directory". Use the
201 corresponding global variable as in all other places of the module.
202 trunk patch: http://svn.apache.org/r1719257
203 2.4.x patch: trunk works
204 +1: jailletc36, covener, jim
206 *) mod_ssl: Save some TLS record (application data) fragmentations by
207 including the last and subsequent suitable buckets when coalescing.
208 trunk patch: http://svn.apache.org/r1723122
209 http://svn.apache.org/r1723143
210 http://svn.apache.org/r1723284
211 2.4.x patch: trunk works, modulo CHANGES (from both r1723122,1723284)
212 For convenience (possibly):
213 http://people.apache.org/~ylavic/httpd-2.4.x-ssl_io_filter_coalesce.patch
216 *) mime.types: Add common extension "m4a" for MPEG 4 Audio.
217 As a reference see Wikipedia:
218 https://en.wikipedia.org/wiki/MPEG-4_Part_14#.MP4_versus_.M4A
220 trunk patch: http://svn.apache.org/r1723567
221 2.4.x patch: trunk works, modulo CHANGES
222 +1: rjung, covener, jim
224 *) mod_rewrite: Avoid looping on relative substitutions that
225 result in the same filename we started with.
227 trunk patch: http://svn.apache.org/r1724656
231 *) mod_cgid: drop severity of flush error message to match
233 trunk patch: http://svn.apache.org/r1724847
237 *) mod_proxy_fcgi: Suppress HTTP error 503 and message 01075,
238 "Error dispatching request", when the cause appears to be
239 the client closing the connection. PR58118
240 trunk patch: http://svn.apache.org/r1724857
241 2.4.x patch: trunk works
244 *) core: Add expr= support to SetHandler (someone wanted this in
245 a well-articulated serverfault post).
246 trunk patch: http://svn.apache.org/r1725149
247 http://svn.apache.org/r1725151
248 2.4.x patch: MMN/changes only: http://people.apache.org/~covener/patches/2.4.x-sethandler-expr.diff
251 PATCHES/ISSUES THAT ARE BEING WORKED
253 *) http: Don't remove the Content-Length of zero from a HEAD response if
254 it comes from an origin server, module or script. Allow the previous
255 behaviour (for legacy/buggy modules only, not origin) by also backporting
256 the HttpContentLengthHeadZero directive (and also HttpExpectStrict which
257 comes for free with the same commit).
258 trunk patch: http://svn.apache.org/r1554303
259 http://svn.apache.org/r1678215
260 2.4.x patch: http://people.apache.org/~ylavic/httpd-2.4.x-preserve_head_cl_zero.patch
262 ylavic: r1554303 issued a major MMN bump, but since the ABI change is two
263 ints added at the end of core_server_config, the proposed merge
264 does a minor bump only.
265 minfrin: Two new directives need to be documented.
267 * mod_proxy_http: Don't establish or reuse a backend connection before pre-
268 fetching the request body, so to minimize the delay between it is supposed
269 to be alive and the first bytes sent: this is a best effort to prevent the
270 backend from closing because of idle or keepalive timeout in the meantime.
271 Also, handle a new "proxy-flushall" environment variable which allows to
272 flush any forwarded body data immediately. PR 56541+37920.
273 trunk patch: http://svn.apache.org/r1656259
274 http://svn.apache.org/r1656359 (CHANGES entry)
275 2.4.x patch: trunk works (modulo CHANGES, docs/log-message-tags)
277 -0: jim: This seems to be a hit to normal performance, to handle an
278 error and/or non-normal condition. The pre-fetch is
279 expensive, and is always done, even before we know that
280 the backend is available to rec' it. I understand the
281 error described, but is the fix actually worth it (plus
282 it seems to allow for a DDoS vector).
283 ylavic: It seems to me that the problem is real since we reuse the
284 connection before prefetching 16K (either controlled by the
285 client, or by an input filter), we currently always prefetch
286 these bytes already. Regarding performance I don't see any
287 difference (more cycles) compared with the current code.
288 However I think I failed to rebuild the header_brigade when
289 the proxy loop is retried (ping), so I need to rework this.
290 Do you think we'd better remove the prefetch, or maybe just
291 make it nonblocking (by default)?
292 jim: Non-blocking seems the best way to handle...
294 PATCHES/ISSUES THAT ARE STALLED
296 * core: Add ap_errorlog_provider to make ErrorLog logging modular. This
297 backport keeps syslog logging as part of httpd core and only adds
298 API to allow other modules to be used for error logging.
299 trunk patch: http://svn.apache.org/r1525597
300 http://svn.apache.org/r1525664
301 http://svn.apache.org/r1525845
302 http://svn.apache.org/r1527003
303 http://svn.apache.org/r1527005
304 http://svn.apache.org/r1532344
305 http://svn.apache.org/r1539988
306 http://svn.apache.org/r1541029
307 http://svn.apache.org/r1543979
308 http://svn.apache.org/r1544156
309 http://svn.apache.org/r1626978
310 2.4.x patch: http://people.apache.org/~jkaluza/patches/httpd-2.4.x-errorlog_provider.patch
312 +1: covener w/ doc or code to fix syntax (providername:providerarg not supported like syslog or socacheproviders,
313 needs 2 args which is not valid in ErrorLog manual)
314 trawick: nit: fix "writing" in "/* NULL if we are writting to syslog */"
315 (sorry, haven't finished reviewing completely)
316 jim: What is the status of this??
318 * mod_proxy: Add ap_proxy_define_match_worker() and use it for ProxyPassMatch
319 and ProxyMatch section to distinguish between normal workers and workers
320 with regex substitutions in the name. Implement handling of such workers
321 in ap_proxy_get_worker(). Fixes the bug when regex workers were not
322 matched and used for request. PR 43513.
323 trunk patch: http://svn.apache.org/r1609680
324 http://svn.apache.org/r1609688
325 http://svn.apache.org/r1641381
326 ylavic: Merge patch provided (reusing new->real to avoid double de_socketfy() call).
327 Also added missing r1609688 to the patchset.
328 2.4.x patch: http://people.apache.org/~ylavic/httpd-2.4.x-ap_proxy_define_match_worker.patch
330 -0: covener tried to review this one in Austin with Jeff. Does the added match function
331 really cover a very narrow set of parameters with the way it skips over backreferences?
332 Also, why a new API vs. just setting the field inline?
334 * mod_systemd: New module, for integration with systemd on Linux.
335 trunk patch: http://svn.apache.org/r1393976
336 http://svn.apache.org/r1393997
337 http://svn.apache.org/r1484554
338 http://svn.apache.org/r1528032
339 http://svn.apache.org/r1528034
340 http://svn.apache.org/r1614821
341 http://svn.apache.org/r1618579
342 http://svn.apache.org/r1618588
343 2.4.x patch: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-mod_systemd.patch
346 * mod_journald: Add new module mod_journald to log error logs into journald.
347 This patch needs changes done in mod_systemd patch (already
349 trunk patch: http://svn.apache.org/r1610339
350 http://svn.apache.org/r1621806
351 2.4.x patch: http://people.apache.org/~jkaluza/patches/httpd-2.4.x-mod_journald.patch
353 rjung, minfrin: Not understanding "This patch needs changes done in
354 mod_systemd patch", am I right in understanding this patch is
356 jkaluza: No, that patch is not committed yet. It is in STALLED section.
357 The link for that patch is: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-mod_systemd.patch
359 * core: Add support for systemd socket activation.
360 trunk patch: http://svn.apache.org/r1511033
361 http://svn.apache.org/r1608686
362 http://svn.apache.org/r1608694
363 http://svn.apache.org/r1608703
364 http://svn.apache.org/r1608721
365 http://svn.apache.org/r1608744
366 2.4.x patch: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-socket-activation.patch
369 * mod_proxy: Ensure network errors detected by the proxy are returned as
370 504 Gateway Timout as opposed to 502 Bad Gateway
371 trunk patch: https://svn.apache.org/viewvc?view=revision&revision=1480058
372 2.4.x patch: trunk patch works modulo CHANGES
374 -1: rpluem: This change is still disputed. See
375 http://mail-archives.apache.org/mod_mbox/httpd-dev/201305.mbox/%3C1B16B9E3-87BA-4EEF-939C-7C7313B54714%40gbiv.com%3E
377 * cross-compile: allow to provide CC_FOR_BUILD so that gen_test_char will be
378 compiled by the build compiler instead of the host compiler.
379 Also set CC_FOR_BUILD to 'cc' when cross-compilation is detected.
380 Trunk patches: http://svn.apache.org/viewvc?view=revision&revision=1327907
381 http://svn.apache.org/viewvc?view=revision&revision=1328390
382 http://svn.apache.org/viewvc?view=revision&revision=1328714
383 2.4 patch: http://people.apache.org/~fuankg/diffs/httpd-2.4.x-cross_compile.diff
384 fuankg: on hold until we agree for a better and more simple solution ...
386 * Makefile.win: Added copying of .vbs / .wsf CGIs to Windows install target.
387 Moved fixing of shebang to separate target so that it is
388 no longer executed by default and all CGIs remain inactive.
389 trunk patch: http://svn.apache.org/viewvc?view=revision&revision=1387984
390 http://svn.apache.org/viewvc?view=revision&revision=1421203
391 http://svn.apache.org/viewvc?view=revision&revision=1421591
392 2.4.x patch: http://people.apache.org/~fuankg/diffs/httpd-2.4.x-Makefile.win.diff
395 This commit is essentially deciding that an httpd install on
396 Windows now has printenv/testcgi written in 2 more languages.
397 To the extent that the usefulness is that it shows how to make scripts
398 of these types executable by httpd, I believe that the documentation
399 is the proper place to solve that. To the extent that the usefullness
400 is to show how to implement a CGI in these particular languages, I believe
401 that the httpd distribution and documentation in general is not the
402 place for that. Historically these types of scripts have caused problems
403 for downstream vendorsas well as newbies (and sometimes the intersection
404 of those two groups) who don't understand that these are information leaks
405 once they are enabled, and the subtlety of the way they are disabled ("Apache
406 messed up the first line; let me fix that") contributes to that.
407 fuankg notes: I've just added a big warning to all CGI scripts which should now
408 make absolutely clear that these CGIs are for testing purpose only - so those
409 who enable those scripts with inserting the right shebang should be 100% aware
410 of any risks (this should cover your last point).
411 jim: trawick, does the above address your concerns?
412 trawick: to some extent (somebody reading the script gets an idea)
413 Why isn't the configuration requirement documented instead
414 of described indirectly in a sample?
415 Why are these new samples added to the install without three
416 votes? (I didn't veto it; put your name next to the two
417 existing ones and I'll be satisified that enough people
418 considered this addition as an appropriate solution for a
419 real httpd usability problem.)
420 wrowe: I'd agree with trawick, and suggest that these scripts can begin
421 their life somewhere in the manual/ tree. This really seems like
422 the place where /usr/share/httpd/examples/ would be useful, but
423 there isn't an ordinary directory for that. Since we want none
424 of the scripts to function 'out of the box', what about a new
425 cgi-examples/ dir alongside cgi-bin/? Otherwise manual/cgi/examples