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. Proposed T&R week of Oct 5th. jim will RM.
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 * mod_journald: Add new module mod_journald to log error logs into journald.
119 This patch needs changes done in mod_systemd patch (already
121 trunk patch: http://svn.apache.org/r1610339
122 http://svn.apache.org/r1621806
123 2.4.x patch: http://people.apache.org/~jkaluza/patches/httpd-2.4.x-mod_journald.patch
125 rjung, minfrin: Not understanding "This patch needs changes done in
126 mod_systemd patch", am I right in understanding this patch is
129 *) http: Don't remove the Content-Length of zero from a HEAD response if
130 it comes from an origin server, module or script. Allow the previous
131 behaviour (for legacy/buggy modules only, not origin) by also backporting
132 the HttpContentLengthHeadZero directive (and also HttpExpectStrict which
133 comes for free with the same commit).
134 trunk patch: http://svn.apache.org/r1554303
135 http://svn.apache.org/r1678215
136 2.4.x patch: http://people.apache.org/~ylavic/httpd-2.4.x-preserve_head_cl_zero.patch
138 ylavic: r1554303 issued a major MMN bump, but since the ABI change is two
139 ints added at the end of core_server_config, the proposed merge
140 does a minor bump only.
141 minfrin: Two new directives need to be documented.
143 *) mod_proxy: don't recyle backend announced "Connection: close" connections
144 to avoid reusing it should the close be effective after some new request
146 trunk patch: http://svn.apache.org/r1678763
147 http://svn.apache.org/r1703807
148 http://svn.apache.org/r1703813
149 2.4.x patch: trunk works (module CHANGES)
151 ylavic: while at it, I also included r1678763 which is only an
152 optimization, but allows to keep code in sync with trunk.
154 *) mod_alias: Introduce expression parser support for Alias, ScriptAlias
155 and Redirect. Limit Redirect expressions to directory (Location) context
156 and redirect statuses (implicit or explicit).
157 trunk patch: http://svn.apache.org/r1653941
158 http://svn.apache.org/r1653978
159 http://svn.apache.org/r1656225
160 http://svn.apache.org/r1686853
161 http://svn.apache.org/r1686856
162 2.4.x patch: https://people.apache.org/~minfrin/httpd-mod_alias-expr2.patch
165 * mod_ssl: Make the output filter more friendly with deferred write and
167 trunk patch: http://svn.apache.org/r1705194
168 http://svn.apache.org/r1705823
169 http://svn.apache.org/r1705826
170 http://svn.apache.org/r1705828
171 http://svn.apache.org/r1705833
172 http://svn.apache.org/r1706275
173 http://svn.apache.org/r1707230
174 http://svn.apache.org/r1707231
175 2.4.x patch: http://people.apache.org/~ylavic/httpd-2.4.x-mod_ssl-deferred_friendly-v3.patch
178 * mod_ssl: Extend expression parser registration to support ssl variables
179 in any expression using mod_rewrite syntax "%{SSL:VARNAME}" or function
180 syntax "ssl(VARIABLE)".
181 trunk patch: http://svn.apache.org/r1707152
182 2.4.x patch: trunk works (modulo CHANGES)
186 PATCHES/ISSUES THAT ARE BEING WORKED
188 * mod_proxy_http: Don't establish or reuse a backend connection before pre-
189 fetching the request body, so to minimize the delay between it is supposed
190 to be alive and the first bytes sent: this is a best effort to prevent the
191 backend from closing because of idle or keepalive timeout in the meantime.
192 Also, handle a new "proxy-flushall" environment variable which allows to
193 flush any forwarded body data immediately. PR 56541+37920.
194 trunk patch: http://svn.apache.org/r1656259
195 http://svn.apache.org/r1656359 (CHANGES entry)
196 2.4.x patch: trunk works (modulo CHANGES, docs/log-message-tags)
198 -0: jim: This seems to be a hit to normal performance, to handle an
199 error and/or non-normal condition. The pre-fetch is
200 expensive, and is always done, even before we know that
201 the backend is available to rec' it. I understand the
202 error described, but is the fix actually worth it (plus
203 it seems to allow for a DDoS vector).
204 ylavic: It seems to me that the problem is real since we reuse the
205 connection before prefetching 16K (either controlled by the
206 client, or by an input filter), we currently always prefetch
207 these bytes already. Regarding performance I don't see any
208 difference (more cycles) compared with the current code.
209 However I think I failed to rebuild the header_brigade when
210 the proxy loop is retried (ping), so I need to rework this.
211 Do you think we'd better remove the prefetch, or maybe just
212 make it nonblocking (by default)?
213 jim: Non-blocking seems the best way to handle...
215 PATCHES/ISSUES THAT ARE STALLED
217 * core: Add ap_errorlog_provider to make ErrorLog logging modular. This
218 backport keeps syslog logging as part of httpd core and only adds
219 API to allow other modules to be used for error logging.
220 trunk patch: http://svn.apache.org/r1525597
221 http://svn.apache.org/r1525664
222 http://svn.apache.org/r1525845
223 http://svn.apache.org/r1527003
224 http://svn.apache.org/r1527005
225 http://svn.apache.org/r1532344
226 http://svn.apache.org/r1539988
227 http://svn.apache.org/r1541029
228 http://svn.apache.org/r1543979
229 http://svn.apache.org/r1544156
230 http://svn.apache.org/r1626978
231 2.4.x patch: http://people.apache.org/~jkaluza/patches/httpd-2.4.x-errorlog_provider.patch
233 +1: covener w/ doc or code to fix syntax (providername:providerarg not supported like syslog or socacheproviders,
234 needs 2 args which is not valid in ErrorLog manual)
235 trawick: nit: fix "writing" in "/* NULL if we are writting to syslog */"
236 (sorry, haven't finished reviewing completely)
237 jim: What is the status of this??
239 * mod_proxy: Add ap_proxy_define_match_worker() and use it for ProxyPassMatch
240 and ProxyMatch section to distinguish between normal workers and workers
241 with regex substitutions in the name. Implement handling of such workers
242 in ap_proxy_get_worker(). Fixes the bug when regex workers were not
243 matched and used for request. PR 43513.
244 trunk patch: http://svn.apache.org/r1609680
245 http://svn.apache.org/r1609688
246 http://svn.apache.org/r1641381
247 ylavic: Merge patch provided (reusing new->real to avoid double de_socketfy() call).
248 Also added missing r1609688 to the patchset.
249 2.4.x patch: http://people.apache.org/~ylavic/httpd-2.4.x-ap_proxy_define_match_worker.patch
251 -0: covener tried to review this one in Austin with Jeff. Does the added match function
252 really cover a very narrow set of parameters with the way it skips over backreferences?
253 Also, why a new API vs. just setting the field inline?
255 * mod_systemd: New module, for integration with systemd on Linux.
256 trunk patch: http://svn.apache.org/r1393976
257 http://svn.apache.org/r1393997
258 http://svn.apache.org/r1484554
259 http://svn.apache.org/r1528032
260 http://svn.apache.org/r1528034
261 http://svn.apache.org/r1614821
262 http://svn.apache.org/r1618579
263 http://svn.apache.org/r1618588
264 2.4.x patch: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-mod_systemd.patch
267 * core: Add support for systemd socket activation.
268 trunk patch: http://svn.apache.org/r1511033
269 http://svn.apache.org/r1608686
270 http://svn.apache.org/r1608694
271 http://svn.apache.org/r1608703
272 http://svn.apache.org/r1608721
273 http://svn.apache.org/r1608744
274 2.4.x patch: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-socket-activation.patch
277 * mod_proxy: Ensure network errors detected by the proxy are returned as
278 504 Gateway Timout as opposed to 502 Bad Gateway
279 trunk patch: https://svn.apache.org/viewvc?view=revision&revision=1480058
280 2.4.x patch: trunk patch works modulo CHANGES
282 -1: rpluem: This change is still disputed. See
283 http://mail-archives.apache.org/mod_mbox/httpd-dev/201305.mbox/%3C1B16B9E3-87BA-4EEF-939C-7C7313B54714%40gbiv.com%3E
285 * cross-compile: allow to provide CC_FOR_BUILD so that gen_test_char will be
286 compiled by the build compiler instead of the host compiler.
287 Also set CC_FOR_BUILD to 'cc' when cross-compilation is detected.
288 Trunk patches: http://svn.apache.org/viewvc?view=revision&revision=1327907
289 http://svn.apache.org/viewvc?view=revision&revision=1328390
290 http://svn.apache.org/viewvc?view=revision&revision=1328714
291 2.4 patch: http://people.apache.org/~fuankg/diffs/httpd-2.4.x-cross_compile.diff
292 fuankg: on hold until we agree for a better and more simple solution ...
294 * Makefile.win: Added copying of .vbs / .wsf CGIs to Windows install target.
295 Moved fixing of shebang to separate target so that it is
296 no longer executed by default and all CGIs remain inactive.
297 trunk patch: http://svn.apache.org/viewvc?view=revision&revision=1387984
298 http://svn.apache.org/viewvc?view=revision&revision=1421203
299 http://svn.apache.org/viewvc?view=revision&revision=1421591
300 2.4.x patch: http://people.apache.org/~fuankg/diffs/httpd-2.4.x-Makefile.win.diff
303 This commit is essentially deciding that an httpd install on
304 Windows now has printenv/testcgi written in 2 more languages.
305 To the extent that the usefulness is that it shows how to make scripts
306 of these types executable by httpd, I believe that the documentation
307 is the proper place to solve that. To the extent that the usefullness
308 is to show how to implement a CGI in these particular languages, I believe
309 that the httpd distribution and documentation in general is not the
310 place for that. Historically these types of scripts have caused problems
311 for downstream vendorsas well as newbies (and sometimes the intersection
312 of those two groups) who don't understand that these are information leaks
313 once they are enabled, and the subtlety of the way they are disabled ("Apache
314 messed up the first line; let me fix that") contributes to that.
315 fuankg notes: I've just added a big warning to all CGI scripts which should now
316 make absolutely clear that these CGIs are for testing purpose only - so those
317 who enable those scripts with inserting the right shebang should be 100% aware
318 of any risks (this should cover your last point).
319 jim: trawick, does the above address your concerns?
320 trawick: to some extent (somebody reading the script gets an idea)
321 Why isn't the configuration requirement documented instead
322 of described indirectly in a sample?
323 Why are these new samples added to the install without three
324 votes? (I didn't veto it; put your name next to the two
325 existing ones and I'll be satisified that enough people
326 considered this addition as an appropriate solution for a
327 real httpd usability problem.)
328 wrowe: I'd agree with trawick, and suggest that these scripts can begin
329 their life somewhere in the manual/ tree. This really seems like
330 the place where /usr/share/httpd/examples/ would be useful, but
331 there isn't an ordinary directory for that. Since we want none
332 of the scripts to function 'out of the box', what about a new
333 cgi-examples/ dir alongside cgi-bin/? Otherwise manual/cgi/examples