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. ]
115 PATCHES PROPOSED TO BACKPORT FROM TRUNK:
116 [ New proposals should be added at the end of the list ]
118 * core: Add ap_errorlog_provider to make ErrorLog logging modular. This
119 backport keeps syslog logging as part of httpd core and only adds
120 API to allow other modules to be used for error logging.
121 trunk patch: http://svn.apache.org/r1525597
122 http://svn.apache.org/r1525664
123 http://svn.apache.org/r1525845
124 http://svn.apache.org/r1527003
125 http://svn.apache.org/r1527005
126 http://svn.apache.org/r1532344
127 http://svn.apache.org/r1539988
128 http://svn.apache.org/r1541029
129 http://svn.apache.org/r1543979
130 http://svn.apache.org/r1544156
131 http://svn.apache.org/r1626978
132 2.4.x patch: http://people.apache.org/~jkaluza/patches/httpd-2.4.x-errorlog_provider.patch
134 +1: covener w/ doc or code to fix syntax (providername:providerarg not supported like syslog or socacheproviders,
135 needs 2 args which is not valid in ErrorLog manual)
136 trawick: nit: fix "writing" in "/* NULL if we are writting to syslog */"
137 (sorry, haven't finished reviewing completely)
138 jim: What is the status of this??
140 * mod_journald: Add new module mod_journald to log error logs into journald.
141 This patch needs changes done in mod_systemd patch (already
143 trunk patch: http://svn.apache.org/r1610339
144 http://svn.apache.org/r1621806
145 2.4.x patch: http://people.apache.org/~jkaluza/patches/httpd-2.4.x-mod_journald.patch
147 minfrin: Not understanding "This patch needs changes done in
148 mod_systemd patch", am I right in understanding this patch is
151 *) http: Don't remove the Content-Length of zero from a HEAD response if
152 it comes from an origin server, module or script. Allow the previous
153 behaviour (for legacy/buggy modules only, not origin) by also backporting
154 the HttpContentLengthHeadZero directive (and also HttpExpectStrict which
155 comes for free with the same commit).
156 trunk patch: http://svn.apache.org/r1554303
157 http://svn.apache.org/r1678215
158 2.4.x patch: http://people.apache.org/~ylavic/httpd-2.4.x-preserve_head_cl_zero.patch
160 ylavic: r1554303 issued a major MMN bump, but since the ABI change is two
161 ints added at the end of core_server_config, the proposed merge
162 does a minor bump only.
163 minfrin: Two new directives need to be documented.
165 *) mod_substitute: Configure patterns merge order. PR 57641
166 trunk patch: http://svn.apache.org/r1684900
167 http://svn.apache.org/r1687539
168 http://svn.apache.org/r1687680
169 http://svn.apache.org/r1688331
170 http://svn.apache.org/r1688339
171 http://svn.apache.org/r1688340
172 http://svn.apache.org/r1688343
173 http://svn.apache.org/r1697013
174 http://svn.apache.org/r1697015
175 2.4.x patch: http://people.apache.org/~ylavic/httpd-2.4.x-SubstituteInheritBefore-v5.patch
177 ylavic: updated to v5 including r1697013 and r1697015, the diff to v4 is:
178 http://people.apache.org/~ylavic/httpd-2.4.x-SubstituteInheritBefore-v4_vs_v5.diff
180 *) mod_proxy: don't recyle backend announced "Connection: close" connections
181 to avoid reusing it should the close be effective after some new request
183 trunk patch: http://svn.apache.org/r1678763
184 http://svn.apache.org/r1703807
185 http://svn.apache.org/r1703813
186 2.4.x patch: trunk works (module CHANGES)
188 ylavic: while at it, I also included r1678763 which is only an
189 optimization, but allows to keep code in sync with trunk.
191 *) mod_proxy: Fix ProxySourceAddress binding failure with AH00938. PR 56687.
192 trunk patch: http://svn.apache.org/r1703902
193 2.4.x patch: trunk works (module CHANGES)
196 *) mod_ssl: namespacing changes from May 2015
197 trunk patches: https://svn.apache.org/r1674538
198 https://svn.apache.org/r1677143
199 https://svn.apache.org/r1677144
200 https://svn.apache.org/r1677145
201 https://svn.apache.org/r1677146
202 https://svn.apache.org/r1677149
203 https://svn.apache.org/r1677151
204 https://svn.apache.org/r1677153
205 https://svn.apache.org/r1677154
206 https://svn.apache.org/r1677155
207 https://svn.apache.org/r1677156
208 https://svn.apache.org/r1677159
209 https://svn.apache.org/r1677339
210 https://svn.apache.org/r1677830
211 https://svn.apache.org/r1677832
212 https://svn.apache.org/r1677834
213 https://svn.apache.org/r1677835
214 2.4.x patch: https://people.apache.org/~kbrand/mod_ssl-2.4.x-namespacing.diff
217 *) mod_ssl: add support for msUPN and dnsSRV otherName form entries
218 in the subjectAltName extension. PR 58020.
219 trunk patch: https://svn.apache.org/r1693792
220 2.4.x patch: trunk works (modulo CHANGES),
221 but depends on the namespacing backport (see above)
224 *) mod_ssl: support SUITEB* cipher strings with OpenSSL 1.0.2 and later.
226 trunk patch: https://svn.apache.org/r1702643
227 2.4.x patch: trunk works (modulo CHANGES)
230 *) mod_ssl: Support compilation against libssl built with OPENSSL_NO_SSL3,
231 and change the compiled-in default for SSL[Proxy]Protocol to "all -SSLv3".
233 trunk patch: https://svn.apache.org/r1703952
234 2.4.x patch: https://people.apache.org/~kbrand/mod_ssl-2.4.x-disable-sslv3.diff
236 ylavic: Should we really change the (implicit) default in 2.4.x at
237 this stage (and potentially break existing configuratios w/o
238 SSLProtocol which used to work with SSLv3 only capable clients)?
240 *) mod_alias: Introduce expression parser support for Alias, ScriptAlias
241 and Redirect. Limit Redirect expressions to directory (Location) context
242 and redirect statuses (implicit or explicit).
243 trunk patch: http://svn.apache.org/r1653941
244 http://svn.apache.org/r1653978
245 http://svn.apache.org/r1656225
246 http://svn.apache.org/r1686853
247 http://svn.apache.org/r1686856
248 2.4.x patch: https://people.apache.org/~minfrin/httpd-mod_alias-expr2.patch
251 * MPMs: Follow up to r1705492 (SO_REUSEPORT). Add missing (and harmless)
252 backport hunk (for consistency with trunk and 2.4.x's worker/event).
253 trunk patch: http://svn.apache.org/r1629916
254 2.4.x patch: trunk works
258 PATCHES/ISSUES THAT ARE BEING WORKED
260 * mod_proxy_http: Don't establish or reuse a backend connection before pre-
261 fetching the request body, so to minimize the delay between it is supposed
262 to be alive and the first bytes sent: this is a best effort to prevent the
263 backend from closing because of idle or keepalive timeout in the meantime.
264 Also, handle a new "proxy-flushall" environment variable which allows to
265 flush any forwarded body data immediately. PR 56541+37920.
266 trunk patch: http://svn.apache.org/r1656259
267 http://svn.apache.org/r1656359 (CHANGES entry)
268 2.4.x patch: trunk works (modulo CHANGES, docs/log-message-tags)
270 -0: jim: This seems to be a hit to normal performance, to handle an
271 error and/or non-normal condition. The pre-fetch is
272 expensive, and is always done, even before we know that
273 the backend is available to rec' it. I understand the
274 error described, but is the fix actually worth it (plus
275 it seems to allow for a DDoS vector).
276 ylavic: It seems to me that the problem is real since we reuse the
277 connection before prefetching 16K (either controlled by the
278 client, or by an input filter), we currently always prefetch
279 these bytes already. Regarding performance I don't see any
280 difference (more cycles) compared with the current code.
281 However I think I failed to rebuild the header_brigade when
282 the proxy loop is retried (ping), so I need to rework this.
283 Do you think we'd better remove the prefetch, or maybe just
284 make it nonblocking (by default)?
285 jim: Non-blocking seems the best way to handle...
287 PATCHES/ISSUES THAT ARE STALLED
289 * mod_proxy: Add ap_proxy_define_match_worker() and use it for ProxyPassMatch
290 and ProxyMatch section to distinguish between normal workers and workers
291 with regex substitutions in the name. Implement handling of such workers
292 in ap_proxy_get_worker(). Fixes the bug when regex workers were not
293 matched and used for request. PR 43513.
294 trunk patch: http://svn.apache.org/r1609680
295 http://svn.apache.org/r1609688
296 http://svn.apache.org/r1641381
297 ylavic: Merge patch provided (reusing new->real to avoid double de_socketfy() call).
298 Also added missing r1609688 to the patchset.
299 2.4.x patch: http://people.apache.org/~ylavic/httpd-2.4.x-ap_proxy_define_match_worker.patch
301 -0: covener tried to review this one in Austin with Jeff. Does the added match function
302 really cover a very narrow set of parameters with the way it skips over backreferences?
303 Also, why a new API vs. just setting the field inline?
305 * mod_systemd: New module, for integration with systemd on Linux.
306 trunk patch: http://svn.apache.org/r1393976
307 http://svn.apache.org/r1393997
308 http://svn.apache.org/r1484554
309 http://svn.apache.org/r1528032
310 http://svn.apache.org/r1528034
311 http://svn.apache.org/r1614821
312 http://svn.apache.org/r1618579
313 http://svn.apache.org/r1618588
314 2.4.x patch: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-mod_systemd.patch
317 * core: Add support for systemd socket activation.
318 trunk patch: http://svn.apache.org/r1511033
319 http://svn.apache.org/r1608686
320 http://svn.apache.org/r1608694
321 http://svn.apache.org/r1608703
322 http://svn.apache.org/r1608721
323 http://svn.apache.org/r1608744
324 2.4.x patch: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-socket-activation.patch
327 * mod_proxy: Ensure network errors detected by the proxy are returned as
328 504 Gateway Timout as opposed to 502 Bad Gateway
329 trunk patch: https://svn.apache.org/viewvc?view=revision&revision=1480058
330 2.4.x patch: trunk patch works modulo CHANGES
332 -1: rpluem: This change is still disputed. See
333 http://mail-archives.apache.org/mod_mbox/httpd-dev/201305.mbox/%3C1B16B9E3-87BA-4EEF-939C-7C7313B54714%40gbiv.com%3E
335 * cross-compile: allow to provide CC_FOR_BUILD so that gen_test_char will be
336 compiled by the build compiler instead of the host compiler.
337 Also set CC_FOR_BUILD to 'cc' when cross-compilation is detected.
338 Trunk patches: http://svn.apache.org/viewvc?view=revision&revision=1327907
339 http://svn.apache.org/viewvc?view=revision&revision=1328390
340 http://svn.apache.org/viewvc?view=revision&revision=1328714
341 2.4 patch: http://people.apache.org/~fuankg/diffs/httpd-2.4.x-cross_compile.diff
342 fuankg: on hold until we agree for a better and more simple solution ...
344 * Makefile.win: Added copying of .vbs / .wsf CGIs to Windows install target.
345 Moved fixing of shebang to separate target so that it is
346 no longer executed by default and all CGIs remain inactive.
347 trunk patch: http://svn.apache.org/viewvc?view=revision&revision=1387984
348 http://svn.apache.org/viewvc?view=revision&revision=1421203
349 http://svn.apache.org/viewvc?view=revision&revision=1421591
350 2.4.x patch: http://people.apache.org/~fuankg/diffs/httpd-2.4.x-Makefile.win.diff
353 This commit is essentially deciding that an httpd install on
354 Windows now has printenv/testcgi written in 2 more languages.
355 To the extent that the usefulness is that it shows how to make scripts
356 of these types executable by httpd, I believe that the documentation
357 is the proper place to solve that. To the extent that the usefullness
358 is to show how to implement a CGI in these particular languages, I believe
359 that the httpd distribution and documentation in general is not the
360 place for that. Historically these types of scripts have caused problems
361 for downstream vendorsas well as newbies (and sometimes the intersection
362 of those two groups) who don't understand that these are information leaks
363 once they are enabled, and the subtlety of the way they are disabled ("Apache
364 messed up the first line; let me fix that") contributes to that.
365 fuankg notes: I've just added a big warning to all CGI scripts which should now
366 make absolutely clear that these CGIs are for testing purpose only - so those
367 who enable those scripts with inserting the right shebang should be 100% aware
368 of any risks (this should cover your last point).
369 jim: trawick, does the above address your concerns?
370 trawick: to some extent (somebody reading the script gets an idea)
371 Why isn't the configuration requirement documented instead
372 of described indirectly in a sample?
373 Why are these new samples added to the install without three
374 votes? (I didn't veto it; put your name next to the two
375 existing ones and I'll be satisified that enough people
376 considered this addition as an appropriate solution for a
377 real httpd usability problem.)
378 wrowe: I'd agree with trawick, and suggest that these scripts can begin
379 their life somewhere in the manual/ tree. This really seems like
380 the place where /usr/share/httpd/examples/ would be useful, but
381 there isn't an ordinary directory for that. Since we want none
382 of the scripts to function 'out of the box', what about a new
383 cgi-examples/ dir alongside cgi-bin/? Otherwise manual/cgi/examples