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.17 : In development.
38 2.4.16 : Tagged on July 9, 2015. Released July 15, 2015
39 2.4.15 : Tagged on June 19, 2015. Not released.
40 2.4.14 : Tagged on June 11, 2015. Not released.
41 2.4.13 : Tagged on June 4, 2015. Not released.
42 2.4.12 : Tagged on January 22, 2015. Released Jan 29, 2015
43 2.4.11 : Tagged on January 15, 2015. Not released.
44 2.4.10 : Tagged on July 15, 2014. Released July 21, 2014
45 2.4.9 : Tagged on March 13, 2014. Released on March 17, 2014
46 2.4.8 : Tagged on March 11, 2014. Not released.
47 2.4.7 : Tagged on November 19, 2013. Released on Nov 25, 2013
48 2.4.6 : Tagged on July 15, 2013. Released July, 22, 2013
49 2.4.5 : Tagged on July 11, 2013, not released.
50 2.4.4 : Tagged on February 18, 2013. Released Feb 25, 2013
51 2.4.3 : Tagged on August 17, 2012. Released Aug 18, 2012
52 2.4.2 : Tagged on April 5, 2012. Released Apr 17, 2012.
53 2.4.1 : Tagged on February 13, 2012. Released Feb 21, 2012.
54 2.4.0 : Tagged on January 16, 2012, not released.
55 2.3.16 : Tagged on December 15, 2011.
56 2.3.15 : Tagged on November 8, 2011. Released Nov. 15, 2011.
57 2.3.14 : Tagged on August 1, 2011. Released Aug. 9, 2011.
58 2.3.13 : Tagged on June 28, 2011, not released.
59 2.3.12 : Tagged on May 11, 2011. Released May 23, 2011.
60 2.3.11 : Released as Beta on March 7, 2011.
61 2.3.10 : Tagged on December 13, 2010. Released Dec 21, 2010.
62 2.3.9 : Tagged on November 23, 2010, not released.
63 2.3.8 : Tagged on August 24, 2010.
64 2.3.7 : Tagged on August 19, 2010, not released.
65 2.3.6 : Released on June 21, 2010.
66 2.3.5 : Released on January 26, 2010.
67 2.3.4 : Released on December 8, 2009.
68 2.3.3 : Tagged on November 11, 2009, not released.
69 2.3.2 : Tagged on March 23, 2009, not released.
70 2.3.1 : Tagged on January 2, 2009, not released.
71 2.3.0 : Tagged on December 6, 2008, not released.
73 Contributors looking for a mission:
75 * Just do an egrep on "TODO" or "XXX" in the source.
77 * Review the bug database at: http://issues.apache.org/bugzilla/
79 * Review the "PatchAvailable" bugs in the bug database:
81 https://issues.apache.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Apache+httpd-2&keywords=PatchAvailable
83 After testing, you can append a comment saying "Reviewed and tested".
85 * Open bugs in the bug database.
87 * See also the STATUS file in the docs/ directory, which lists documentation-specific TODO items.
90 CURRENT RELEASE NOTES:
92 * Forward binary compatibility is expected of Apache 2.4.x releases, such
93 that no MMN major number changes will occur after 2.4.1. Such changes can
94 only be made in the trunk.
96 * All commits to branches/2.4.x must be reflected in SVN trunk,
97 as well, if they apply. Logical progression is commit to trunk
98 then merge into branches/2.4.x, as applicable.
100 * Current exceptions for RTC for this branch:
105 . non-Unix, single-platform code
107 RELEASE SHOWSTOPPERS:
110 PATCHES ACCEPTED TO BACKPORT FROM TRUNK:
111 [ start all new proposals below, under PATCHES PROPOSED. ]
113 *) mod_h2: add HTTP/2 support to httpd, depends on core/mod_ssl changes above
114 2.4.x branch for this and core/mod_ssl: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.17-protocols-http2
115 See diff and merged changelists via:
116 svn diff ^/httpd/httpd/branches/2.4.x ^/httpd/httpd/branches/2.4.17-protocols-http2
117 +1: icing, jim, ylavic
120 PATCHES PROPOSED TO BACKPORT FROM TRUNK:
121 [ New proposals should be added at the end of the list ]
123 * core: Add ap_errorlog_provider to make ErrorLog logging modular. This
124 backport keeps syslog logging as part of httpd core and only adds
125 API to allow other modules to be used for error logging.
126 trunk patch: http://svn.apache.org/r1525597
127 http://svn.apache.org/r1525664
128 http://svn.apache.org/r1525845
129 http://svn.apache.org/r1527003
130 http://svn.apache.org/r1527005
131 http://svn.apache.org/r1532344
132 http://svn.apache.org/r1539988
133 http://svn.apache.org/r1541029
134 http://svn.apache.org/r1543979
135 http://svn.apache.org/r1544156
136 http://svn.apache.org/r1626978
137 2.4.x patch: http://people.apache.org/~jkaluza/patches/httpd-2.4.x-errorlog_provider.patch
139 +1: covener w/ doc or code to fix syntax (providername:providerarg not supported like syslog or socacheproviders,
140 needs 2 args which is not valid in ErrorLog manual)
141 trawick: nit: fix "writing" in "/* NULL if we are writting to syslog */"
142 (sorry, haven't finished reviewing completely)
143 jim: What is the status of this??
145 * mod_journald: Add new module mod_journald to log error logs into journald.
146 This patch needs changes done in mod_systemd patch (already
148 trunk patch: http://svn.apache.org/r1610339
149 http://svn.apache.org/r1621806
150 2.4.x patch: http://people.apache.org/~jkaluza/patches/httpd-2.4.x-mod_journald.patch
152 minfrin: Not understanding "This patch needs changes done in
153 mod_systemd patch", am I right in understanding this patch is
156 *) http: Don't remove the Content-Length of zero from a HEAD response if
157 it comes from an origin server, module or script. Allow the previous
158 behaviour (for legacy/buggy modules only, not origin) by also backporting
159 the HttpContentLengthHeadZero directive (and also HttpExpectStrict which
160 comes for free with the same commit).
161 trunk patch: http://svn.apache.org/r1554303
162 http://svn.apache.org/r1678215
163 2.4.x patch: http://people.apache.org/~ylavic/httpd-2.4.x-preserve_head_cl_zero.patch
165 ylavic: r1554303 issued a major MMN bump, but since the ABI change is two
166 ints added at the end of core_server_config, the proposed merge
167 does a minor bump only.
168 minfrin: Two new directives need to be documented.
170 *) mod_substitute: Configure patterns merge order. PR 57641
171 trunk patch: http://svn.apache.org/r1684900
172 http://svn.apache.org/r1687539
173 http://svn.apache.org/r1687680
174 http://svn.apache.org/r1688331
175 http://svn.apache.org/r1688339
176 http://svn.apache.org/r1688340
177 http://svn.apache.org/r1688343
178 http://svn.apache.org/r1697013
179 http://svn.apache.org/r1697015
180 2.4.x patch: http://people.apache.org/~ylavic/httpd-2.4.x-SubstituteInheritBefore-v5.patch
182 ylavic: updated to v5 including r1697013 and r1697015, the diff to v4 is:
183 http://people.apache.org/~ylavic/httpd-2.4.x-SubstituteInheritBefore-v4_vs_v5.diff
185 *) mod_proxy: don't recyle backend announced "Connection: close" connections
186 to avoid reusing it should the close be effective after some new request
188 trunk patch: http://svn.apache.org/r1678763
189 http://svn.apache.org/r1703807
190 http://svn.apache.org/r1703813
191 2.4.x patch: trunk works (module CHANGES)
193 ylavic: while at it, I also included r1678763 which is only an
194 optimization, but allows to keep code in sync with trunk.
196 *) mod_proxy: Fix ProxySourceAddress binding failure with AH00938. PR 56687.
197 trunk patch: http://svn.apache.org/r1703902
198 2.4.x patch: trunk works (module CHANGES)
201 *) mod_ssl: namespacing changes from May 2015
202 trunk patches: https://svn.apache.org/r1674538
203 https://svn.apache.org/r1677143
204 https://svn.apache.org/r1677144
205 https://svn.apache.org/r1677145
206 https://svn.apache.org/r1677146
207 https://svn.apache.org/r1677149
208 https://svn.apache.org/r1677151
209 https://svn.apache.org/r1677153
210 https://svn.apache.org/r1677154
211 https://svn.apache.org/r1677155
212 https://svn.apache.org/r1677156
213 https://svn.apache.org/r1677159
214 https://svn.apache.org/r1677339
215 https://svn.apache.org/r1677830
216 https://svn.apache.org/r1677832
217 https://svn.apache.org/r1677834
218 https://svn.apache.org/r1677835
219 2.4.x patch: https://people.apache.org/~kbrand/mod_ssl-2.4.x-namespacing.diff
222 *) mod_ssl: add support for msUPN and dnsSRV otherName form entries
223 in the subjectAltName extension. PR 58020.
224 trunk patch: https://svn.apache.org/r1693792
225 2.4.x patch: trunk works (modulo CHANGES),
226 but depends on the namespacing backport (see above)
229 *) mod_ssl: support SUITEB* cipher strings with OpenSSL 1.0.2 and later.
231 trunk patch: https://svn.apache.org/r1702643
232 2.4.x patch: trunk works (modulo CHANGES)
235 *) mod_ssl: Support compilation against libssl built with OPENSSL_NO_SSL3,
236 and change the compiled-in default for SSL[Proxy]Protocol to "all -SSLv3".
238 trunk patch: https://svn.apache.org/r1703952
239 2.4.x patch: https://people.apache.org/~kbrand/mod_ssl-2.4.x-disable-sslv3.diff
241 ylavic: Should we really change the (implicit) default in 2.4.x at
242 this stage (and potentially break existing configuratios w/o
243 SSLProtocol which used to work with SSLv3 only capable clients)?
245 *) mod_alias: Introduce expression parser support for Alias, ScriptAlias
246 and Redirect. Limit Redirect expressions to directory (Location) context
247 and redirect statuses (implicit or explicit).
248 trunk patch: http://svn.apache.org/r1653941
249 http://svn.apache.org/r1653978
250 http://svn.apache.org/r1656225
251 http://svn.apache.org/r1686853
252 http://svn.apache.org/r1686856
253 2.4.x patch: https://people.apache.org/~minfrin/httpd-mod_alias-expr2.patch
256 * MPMs: Follow up to r1705492 (SO_REUSEPORT). Add missing (and harmless)
257 backport hunk (for consistency with trunk and 2.4.x's worker/event).
258 trunk patch: http://svn.apache.org/r1629916
259 2.4.x patch: trunk works
263 PATCHES/ISSUES THAT ARE BEING WORKED
265 * mod_proxy_http: Don't establish or reuse a backend connection before pre-
266 fetching the request body, so to minimize the delay between it is supposed
267 to be alive and the first bytes sent: this is a best effort to prevent the
268 backend from closing because of idle or keepalive timeout in the meantime.
269 Also, handle a new "proxy-flushall" environment variable which allows to
270 flush any forwarded body data immediately. PR 56541+37920.
271 trunk patch: http://svn.apache.org/r1656259
272 http://svn.apache.org/r1656359 (CHANGES entry)
273 2.4.x patch: trunk works (modulo CHANGES, docs/log-message-tags)
275 -0: jim: This seems to be a hit to normal performance, to handle an
276 error and/or non-normal condition. The pre-fetch is
277 expensive, and is always done, even before we know that
278 the backend is available to rec' it. I understand the
279 error described, but is the fix actually worth it (plus
280 it seems to allow for a DDoS vector).
281 ylavic: It seems to me that the problem is real since we reuse the
282 connection before prefetching 16K (either controlled by the
283 client, or by an input filter), we currently always prefetch
284 these bytes already. Regarding performance I don't see any
285 difference (more cycles) compared with the current code.
286 However I think I failed to rebuild the header_brigade when
287 the proxy loop is retried (ping), so I need to rework this.
288 Do you think we'd better remove the prefetch, or maybe just
289 make it nonblocking (by default)?
290 jim: Non-blocking seems the best way to handle...
292 PATCHES/ISSUES THAT ARE STALLED
294 * mod_proxy: Add ap_proxy_define_match_worker() and use it for ProxyPassMatch
295 and ProxyMatch section to distinguish between normal workers and workers
296 with regex substitutions in the name. Implement handling of such workers
297 in ap_proxy_get_worker(). Fixes the bug when regex workers were not
298 matched and used for request. PR 43513.
299 trunk patch: http://svn.apache.org/r1609680
300 http://svn.apache.org/r1609688
301 http://svn.apache.org/r1641381
302 ylavic: Merge patch provided (reusing new->real to avoid double de_socketfy() call).
303 Also added missing r1609688 to the patchset.
304 2.4.x patch: http://people.apache.org/~ylavic/httpd-2.4.x-ap_proxy_define_match_worker.patch
306 -0: covener tried to review this one in Austin with Jeff. Does the added match function
307 really cover a very narrow set of parameters with the way it skips over backreferences?
308 Also, why a new API vs. just setting the field inline?
310 * mod_systemd: New module, for integration with systemd on Linux.
311 trunk patch: http://svn.apache.org/r1393976
312 http://svn.apache.org/r1393997
313 http://svn.apache.org/r1484554
314 http://svn.apache.org/r1528032
315 http://svn.apache.org/r1528034
316 http://svn.apache.org/r1614821
317 http://svn.apache.org/r1618579
318 http://svn.apache.org/r1618588
319 2.4.x patch: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-mod_systemd.patch
322 * core: Add support for systemd socket activation.
323 trunk patch: http://svn.apache.org/r1511033
324 http://svn.apache.org/r1608686
325 http://svn.apache.org/r1608694
326 http://svn.apache.org/r1608703
327 http://svn.apache.org/r1608721
328 http://svn.apache.org/r1608744
329 2.4.x patch: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-socket-activation.patch
332 * mod_proxy: Ensure network errors detected by the proxy are returned as
333 504 Gateway Timout as opposed to 502 Bad Gateway
334 trunk patch: https://svn.apache.org/viewvc?view=revision&revision=1480058
335 2.4.x patch: trunk patch works modulo CHANGES
337 -1: rpluem: This change is still disputed. See
338 http://mail-archives.apache.org/mod_mbox/httpd-dev/201305.mbox/%3C1B16B9E3-87BA-4EEF-939C-7C7313B54714%40gbiv.com%3E
340 * cross-compile: allow to provide CC_FOR_BUILD so that gen_test_char will be
341 compiled by the build compiler instead of the host compiler.
342 Also set CC_FOR_BUILD to 'cc' when cross-compilation is detected.
343 Trunk patches: http://svn.apache.org/viewvc?view=revision&revision=1327907
344 http://svn.apache.org/viewvc?view=revision&revision=1328390
345 http://svn.apache.org/viewvc?view=revision&revision=1328714
346 2.4 patch: http://people.apache.org/~fuankg/diffs/httpd-2.4.x-cross_compile.diff
347 fuankg: on hold until we agree for a better and more simple solution ...
349 * Makefile.win: Added copying of .vbs / .wsf CGIs to Windows install target.
350 Moved fixing of shebang to separate target so that it is
351 no longer executed by default and all CGIs remain inactive.
352 trunk patch: http://svn.apache.org/viewvc?view=revision&revision=1387984
353 http://svn.apache.org/viewvc?view=revision&revision=1421203
354 http://svn.apache.org/viewvc?view=revision&revision=1421591
355 2.4.x patch: http://people.apache.org/~fuankg/diffs/httpd-2.4.x-Makefile.win.diff
358 This commit is essentially deciding that an httpd install on
359 Windows now has printenv/testcgi written in 2 more languages.
360 To the extent that the usefulness is that it shows how to make scripts
361 of these types executable by httpd, I believe that the documentation
362 is the proper place to solve that. To the extent that the usefullness
363 is to show how to implement a CGI in these particular languages, I believe
364 that the httpd distribution and documentation in general is not the
365 place for that. Historically these types of scripts have caused problems
366 for downstream vendorsas well as newbies (and sometimes the intersection
367 of those two groups) who don't understand that these are information leaks
368 once they are enabled, and the subtlety of the way they are disabled ("Apache
369 messed up the first line; let me fix that") contributes to that.
370 fuankg notes: I've just added a big warning to all CGI scripts which should now
371 make absolutely clear that these CGIs are for testing purpose only - so those
372 who enable those scripts with inserting the right shebang should be 100% aware
373 of any risks (this should cover your last point).
374 jim: trawick, does the above address your concerns?
375 trawick: to some extent (somebody reading the script gets an idea)
376 Why isn't the configuration requirement documented instead
377 of described indirectly in a sample?
378 Why are these new samples added to the install without three
379 votes? (I didn't veto it; put your name next to the two
380 existing ones and I'll be satisified that enough people
381 considered this addition as an appropriate solution for a
382 real httpd usability problem.)
383 wrowe: I'd agree with trawick, and suggest that these scripts can begin
384 their life somewhere in the manual/ tree. This really seems like
385 the place where /usr/share/httpd/examples/ would be useful, but
386 there isn't an ordinary directory for that. Since we want none
387 of the scripts to function 'out of the box', what about a new
388 cgi-examples/ dir alongside cgi-bin/? Otherwise manual/cgi/examples