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 *) mod_deflate: follow up to r1619444 (and to r1619383). (backported in r1669555)
116 Fix counting of inflated bytes in deflate_in_filter() when
118 trunk patch: http://svn.apache.org/r1619483
119 2.4.x patch: trunk works
120 +1: ylavic, icing, trawick
122 PATCHES PROPOSED TO BACKPORT FROM TRUNK:
123 [ New proposals should be added at the end of the list ]
125 *) mod_proxy_hcheck: Dynamic reverse proxy backend health check module
126 Trunk version of patch: <various>
127 Backport version for 2.4.x of patch:
128 http://home.apache.org/~jim/patches/hcheck-2.4-v2.patch
131 ylavic: Looks like the changes on struct proxy_worker_shared would break
132 startup with "BalancerPersist on" due to the strict checks on
133 the sizes of existing slotmems (slotmem_create/attach)?
134 jim: Yes, that is right (re: breakage)... this would be noted at
136 ylavic: OK, this is just that persisted slotmems won't be reused on first
137 startup, not that the startup will fail (as I first thought).
139 *) core/util_script: relax alphanumeric filter of enviroment variable names
140 on Windows to allow '(' and ')' for passing PROGRAMFILES(X86) et.al.
141 unadulterated in 64 bit versions of Windows. PR 46751.
142 trunk patch: http://svn.apache.org/r1705217
143 2.4.x patch: trunk patch works
145 ylavic: As asked on dev@ (in reply to r1705217), what about CVE-2014-6271
146 (shellshock) with unix-like shells (or even maybe native windows
149 *) mod_ssl: Add "no_crl_for_cert_ok" flag to SSLCARevocationCheck directive
150 to opt-in previous behaviour (2.2) with CRLs verification when checking
151 certificate(s) with no corresponding CRL.
152 trunk patch: http://svn.apache.org/r1734561
153 http://svn.apache.org/r1734807
154 http://svn.apache.org/r1735159
155 http://svn.apache.org/r1735337
156 2.4.x patch: trunk works (modulo CHANGES) or
157 http://home.apache.org/~ylavic/patches/httpd-2.4.x-no_crl_for_cert_ok.patch
160 *) mod_proxy_http2: add http2 proxy support in new, experimental module.
161 Includes backport of r1729208 to set ALPN protocols for ssl backend
163 Trunk version of patch: <various>
164 Backport version for 2.4.x of patch: https://www.eissing.org/proxy_http2_2.4v2.patch
166 updated patch after review by cjaillet, merged 1735668,1735748 from trunk
168 *) mod_authz_host: add "forward-dns" authorization provider
169 trunk patch: http://svn.apache.org/r1734412
170 2.4.x patch: trunk should work (possible minor issue on next-number)
174 PATCHES/ISSUES THAT ARE BEING WORKED
176 *) http: Don't remove the Content-Length of zero from a HEAD response if
177 it comes from an origin server, module or script. Allow the previous
178 behaviour (for legacy/buggy modules only, not origin) by also backporting
179 the HttpContentLengthHeadZero directive (and also HttpExpectStrict which
180 comes for free with the same commit).
181 trunk patch: http://svn.apache.org/r1554303
182 http://svn.apache.org/r1678215
183 2.4.x patch: http://people.apache.org/~ylavic/httpd-2.4.x-preserve_head_cl_zero.patch
185 ylavic: r1554303 issued a major MMN bump, but since the ABI change is two
186 ints added at the end of core_server_config, the proposed merge
187 does a minor bump only.
188 minfrin: Two new directives need to be documented.
190 * mod_proxy_http: Don't establish or reuse a backend connection before pre-
191 fetching the request body, so to minimize the delay between it is supposed
192 to be alive and the first bytes sent: this is a best effort to prevent the
193 backend from closing because of idle or keepalive timeout in the meantime.
194 Also, handle a new "proxy-flushall" environment variable which allows to
195 flush any forwarded body data immediately. PR 56541+37920.
196 trunk patch: http://svn.apache.org/r1656259
197 http://svn.apache.org/r1656359 (CHANGES entry)
198 2.4.x patch: trunk works (modulo CHANGES, docs/log-message-tags)
200 -0: jim: This seems to be a hit to normal performance, to handle an
201 error and/or non-normal condition. The pre-fetch is
202 expensive, and is always done, even before we know that
203 the backend is available to rec' it. I understand the
204 error described, but is the fix actually worth it (plus
205 it seems to allow for a DDoS vector).
206 ylavic: It seems to me that the problem is real since we reuse the
207 connection before prefetching 16K (either controlled by the
208 client, or by an input filter), we currently always prefetch
209 these bytes already. Regarding performance I don't see any
210 difference (more cycles) compared with the current code.
211 However I think I failed to rebuild the header_brigade when
212 the proxy loop is retried (ping), so I need to rework this.
213 Do you think we'd better remove the prefetch, or maybe just
214 make it nonblocking (by default)?
215 jim: Non-blocking seems the best way to handle...
218 PATCHES/ISSUES THAT ARE STALLED
220 * core: Add ap_errorlog_provider to make ErrorLog logging modular. This
221 backport keeps syslog logging as part of httpd core and only adds
222 API to allow other modules to be used for error logging.
223 trunk patch: http://svn.apache.org/r1525597
224 http://svn.apache.org/r1525664
225 http://svn.apache.org/r1525845
226 http://svn.apache.org/r1527003
227 http://svn.apache.org/r1527005
228 http://svn.apache.org/r1532344
229 http://svn.apache.org/r1539988
230 http://svn.apache.org/r1541029
231 http://svn.apache.org/r1543979
232 http://svn.apache.org/r1544156
233 http://svn.apache.org/r1626978
234 2.4.x patch: http://people.apache.org/~jkaluza/patches/httpd-2.4.x-errorlog_provider.patch
236 +1: covener w/ doc or code to fix syntax (providername:providerarg not supported like syslog or socacheproviders,
237 needs 2 args which is not valid in ErrorLog manual)
238 trawick: nit: fix "writing" in "/* NULL if we are writting to syslog */"
239 (sorry, haven't finished reviewing completely)
240 jim: What is the status of this??
242 * mod_proxy: Add ap_proxy_define_match_worker() and use it for ProxyPassMatch
243 and ProxyMatch section to distinguish between normal workers and workers
244 with regex substitutions in the name. Implement handling of such workers
245 in ap_proxy_get_worker(). Fixes the bug when regex workers were not
246 matched and used for request. PR 43513.
247 trunk patch: http://svn.apache.org/r1609680
248 http://svn.apache.org/r1609688
249 http://svn.apache.org/r1641381
250 ylavic: Merge patch provided (reusing new->real to avoid double de_socketfy() call).
251 Also added missing r1609688 to the patchset.
252 2.4.x patch: http://people.apache.org/~ylavic/httpd-2.4.x-ap_proxy_define_match_worker.patch
254 -0: covener tried to review this one in Austin with Jeff. Does the added match function
255 really cover a very narrow set of parameters with the way it skips over backreferences?
256 Also, why a new API vs. just setting the field inline?
258 * mod_systemd: New module, for integration with systemd on Linux.
259 trunk patch: http://svn.apache.org/r1393976
260 http://svn.apache.org/r1393997
261 http://svn.apache.org/r1484554
262 http://svn.apache.org/r1528032
263 http://svn.apache.org/r1528034
264 http://svn.apache.org/r1614821
265 http://svn.apache.org/r1618579
266 http://svn.apache.org/r1618588
267 2.4.x patch: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-mod_systemd.patch
269 sf comments: The IdleShutdown logic seems broken. Consider a single
270 active connection that is stalled for 10 seconds. That
271 connection will be broken after GracefulShutdownTimeout.
272 A better logic would be to check if there is any open
273 connection that is not in keep-alive state.
275 * mod_journald: Add new module mod_journald to log error logs into journald.
276 This patch needs changes done in mod_systemd patch (already
278 trunk patch: http://svn.apache.org/r1610339
279 http://svn.apache.org/r1621806
280 2.4.x patch: http://people.apache.org/~jkaluza/patches/httpd-2.4.x-mod_journald.patch
282 rjung, minfrin: Not understanding "This patch needs changes done in
283 mod_systemd patch", am I right in understanding this patch is
285 jkaluza: No, that patch is not committed yet. It is in STALLED section.
286 The link for that patch is: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-mod_systemd.patch
288 * core: Add support for systemd socket activation.
289 trunk patch: http://svn.apache.org/r1511033
290 http://svn.apache.org/r1608686
291 http://svn.apache.org/r1608694
292 http://svn.apache.org/r1608703
293 http://svn.apache.org/r1608721
294 http://svn.apache.org/r1608744
295 2.4.x patch: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-socket-activation.patch
298 * mod_proxy: Ensure network errors detected by the proxy are returned as
299 504 Gateway Timout as opposed to 502 Bad Gateway
300 trunk patch: https://svn.apache.org/viewvc?view=revision&revision=1480058
301 2.4.x patch: trunk patch works modulo CHANGES
303 -1: rpluem: This change is still disputed. See
304 http://mail-archives.apache.org/mod_mbox/httpd-dev/201305.mbox/%3C1B16B9E3-87BA-4EEF-939C-7C7313B54714%40gbiv.com%3E
306 * cross-compile: allow to provide CC_FOR_BUILD so that gen_test_char will be
307 compiled by the build compiler instead of the host compiler.
308 Also set CC_FOR_BUILD to 'cc' when cross-compilation is detected.
309 Trunk patches: http://svn.apache.org/viewvc?view=revision&revision=1327907
310 http://svn.apache.org/viewvc?view=revision&revision=1328390
311 http://svn.apache.org/viewvc?view=revision&revision=1328714
312 2.4 patch: http://people.apache.org/~fuankg/diffs/httpd-2.4.x-cross_compile.diff
313 fuankg: on hold until we agree for a better and more simple solution ...
315 * Makefile.win: Added copying of .vbs / .wsf CGIs to Windows install target.
316 Moved fixing of shebang to separate target so that it is
317 no longer executed by default and all CGIs remain inactive.
318 trunk patch: http://svn.apache.org/viewvc?view=revision&revision=1387984
319 http://svn.apache.org/viewvc?view=revision&revision=1421203
320 http://svn.apache.org/viewvc?view=revision&revision=1421591
321 2.4.x patch: http://people.apache.org/~fuankg/diffs/httpd-2.4.x-Makefile.win.diff
324 This commit is essentially deciding that an httpd install on
325 Windows now has printenv/testcgi written in 2 more languages.
326 To the extent that the usefulness is that it shows how to make scripts
327 of these types executable by httpd, I believe that the documentation
328 is the proper place to solve that. To the extent that the usefullness
329 is to show how to implement a CGI in these particular languages, I believe
330 that the httpd distribution and documentation in general is not the
331 place for that. Historically these types of scripts have caused problems
332 for downstream vendorsas well as newbies (and sometimes the intersection
333 of those two groups) who don't understand that these are information leaks
334 once they are enabled, and the subtlety of the way they are disabled ("Apache
335 messed up the first line; let me fix that") contributes to that.
336 fuankg notes: I've just added a big warning to all CGI scripts which should now
337 make absolutely clear that these CGIs are for testing purpose only - so those
338 who enable those scripts with inserting the right shebang should be 100% aware
339 of any risks (this should cover your last point).
340 jim: trawick, does the above address your concerns?
341 trawick: to some extent (somebody reading the script gets an idea)
342 Why isn't the configuration requirement documented instead
343 of described indirectly in a sample?
344 Why are these new samples added to the install without three
345 votes? (I didn't veto it; put your name next to the two
346 existing ones and I'll be satisified that enough people
347 considered this addition as an appropriate solution for a
348 real httpd usability problem.)
349 wrowe: I'd agree with trawick, and suggest that these scripts can begin
350 their life somewhere in the manual/ tree. This really seems like
351 the place where /usr/share/httpd/examples/ would be useful, but
352 there isn't an ordinary directory for that. Since we want none
353 of the scripts to function 'out of the box', what about a new
354 cgi-examples/ dir alongside cgi-bin/? Otherwise manual/cgi/examples