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.23 : In development.
38 2.4.22 : Tagged on June 20, 2016.
39 2.4.21 : Tagged on June 16, 2016, not released.
40 2.4.20 : Tagged on April 4, 2016. Released on April 11, 2016.
41 2.4.19 : Tagged on March 21, 2016, not released.
42 2.4.18 : Tagged on December 8, 2015. Released on December 14, 2015.
43 2.4.17 : Tagged on October 9, 2015. Released October 13, 2015.
44 2.4.16 : Tagged on July 9, 2015. Released July 15, 2015
45 2.4.15 : Tagged on June 19, 2015. Not released.
46 2.4.14 : Tagged on June 11, 2015. Not released.
47 2.4.13 : Tagged on June 4, 2015. Not released.
48 2.4.12 : Tagged on January 22, 2015. Released Jan 29, 2015
49 2.4.11 : Tagged on January 15, 2015. Not released.
50 2.4.10 : Tagged on July 15, 2014. Released July 21, 2014
51 2.4.9 : Tagged on March 13, 2014. Released on March 17, 2014
52 2.4.8 : Tagged on March 11, 2014. Not released.
53 2.4.7 : Tagged on November 19, 2013. Released on Nov 25, 2013
54 2.4.6 : Tagged on July 15, 2013. Released July, 22, 2013
55 2.4.5 : Tagged on July 11, 2013, not released.
56 2.4.4 : Tagged on February 18, 2013. Released Feb 25, 2013
57 2.4.3 : Tagged on August 17, 2012. Released Aug 18, 2012
58 2.4.2 : Tagged on April 5, 2012. Released Apr 17, 2012.
59 2.4.1 : Tagged on February 13, 2012. Released Feb 21, 2012.
60 2.4.0 : Tagged on January 16, 2012, not released.
61 2.3.16 : Tagged on December 15, 2011.
62 2.3.15 : Tagged on November 8, 2011. Released Nov. 15, 2011.
63 2.3.14 : Tagged on August 1, 2011. Released Aug. 9, 2011.
64 2.3.13 : Tagged on June 28, 2011, not released.
65 2.3.12 : Tagged on May 11, 2011. Released May 23, 2011.
66 2.3.11 : Released as Beta on March 7, 2011.
67 2.3.10 : Tagged on December 13, 2010. Released Dec 21, 2010.
68 2.3.9 : Tagged on November 23, 2010, not released.
69 2.3.8 : Tagged on August 24, 2010.
70 2.3.7 : Tagged on August 19, 2010, not released.
71 2.3.6 : Released on June 21, 2010.
72 2.3.5 : Released on January 26, 2010.
73 2.3.4 : Released on December 8, 2009.
74 2.3.3 : Tagged on November 11, 2009, not released.
75 2.3.2 : Tagged on March 23, 2009, not released.
76 2.3.1 : Tagged on January 2, 2009, not released.
77 2.3.0 : Tagged on December 6, 2008, not released.
79 Contributors looking for a mission:
81 * Just do an egrep on "TODO" or "XXX" in the source.
83 * Review the bug database at: http://issues.apache.org/bugzilla/
85 * Review the "PatchAvailable" bugs in the bug database:
87 https://issues.apache.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Apache+httpd-2&keywords=PatchAvailable
89 After testing, you can append a comment saying "Reviewed and tested".
91 * Open bugs in the bug database.
93 * See also the STATUS file in the docs/ directory, which lists documentation-specific TODO items.
96 CURRENT RELEASE NOTES:
98 * Forward binary compatibility is expected of Apache 2.4.x releases, such
99 that no MMN major number changes will occur after 2.4.1. Such changes can
100 only be made in the trunk.
102 * All commits to branches/2.4.x must be reflected in SVN trunk,
103 as well, if they apply. Logical progression is commit to trunk
104 then merge into branches/2.4.x, as applicable.
106 * Current exceptions for RTC for this branch:
111 . non-Unix, single-platform code
113 RELEASE SHOWSTOPPERS:
116 PATCHES ACCEPTED TO BACKPORT FROM TRUNK:
117 [ start all new proposals below, under PATCHES PROPOSED. ]
122 PATCHES PROPOSED TO BACKPORT FROM TRUNK:
123 [ New proposals should be added at the end of the list ]
125 *) mod_ssl: Return 502 instead of 500 when SSL peer check or
126 proxy_post_handshake hook fails.
127 Trunk patch: r1645529 (works)
128 2.4.x patch which adds CHANGES: https://emptyhammock.com/media/downloads/r1645529-to-2.4.x.txt
130 ylavic: there may be missing bits, see thread for commit r1736510.
132 *) mod_dav: Add support for childtags to dav_error.
133 trunk patch: http://svn.apache.org/r1746207
134 2.4.x: trunk works modulo CHANGES/MMN
137 *) mod_dav: Add dav_begin_multistatus, dav_send_one_response,
138 dav_finish_multistatus, dav_send_multistatus, dav_handle_err,
139 dav_failed_proppatch, dav_success_proppatch to mod_dav.h.
140 trunk patch: http://svn.apache.org/r1748047
141 2.4.x: trunk works modulo CHANGES/MMN
144 *) core: Drop an invalid Last-Modified header value coming
145 from a FCGI/CGI script instead of replacing it with Unix epoch.
146 trunk patch: http://svn.apache.org/r1748379
147 2.4.x: trunk patch works
150 *) build: Fix issues around mod_proxy_hcheck inclusion.
151 trunk patch: http://svn.apache.org/r1748888
152 2.4.x: trunk patch works
155 PATCHES/ISSUES THAT ARE BEING WORKED
157 *) http: Don't remove the Content-Length of zero from a HEAD response if
158 it comes from an origin server, module or script. Allow the previous
159 behaviour (for legacy/buggy modules only, not origin) by also backporting
160 the HttpContentLengthHeadZero directive (and also HttpExpectStrict which
161 comes for free with the same commit).
162 trunk patch: http://svn.apache.org/r1554303
163 http://svn.apache.org/r1678215
164 2.4.x patch: http://people.apache.org/~ylavic/httpd-2.4.x-preserve_head_cl_zero.patch
166 ylavic: r1554303 issued a major MMN bump, but since the ABI change is two
167 ints added at the end of core_server_config, the proposed merge
168 does a minor bump only.
169 minfrin: Two new directives need to be documented.
171 * mod_proxy_http: Don't establish or reuse a backend connection before pre-
172 fetching the request body, so to minimize the delay between it is supposed
173 to be alive and the first bytes sent: this is a best effort to prevent the
174 backend from closing because of idle or keepalive timeout in the meantime.
175 Also, handle a new "proxy-flushall" environment variable which allows to
176 flush any forwarded body data immediately. PR 56541+37920.
177 trunk patch: http://svn.apache.org/r1656259
178 http://svn.apache.org/r1656359 (CHANGES entry)
179 2.4.x patch: trunk works (modulo CHANGES, docs/log-message-tags)
181 -0: jim: This seems to be a hit to normal performance, to handle an
182 error and/or non-normal condition. The pre-fetch is
183 expensive, and is always done, even before we know that
184 the backend is available to rec' it. I understand the
185 error described, but is the fix actually worth it (plus
186 it seems to allow for a DDoS vector).
187 ylavic: It seems to me that the problem is real since we reuse the
188 connection before prefetching 16K (either controlled by the
189 client, or by an input filter), we currently always prefetch
190 these bytes already. Regarding performance I don't see any
191 difference (more cycles) compared with the current code.
192 However I think I failed to rebuild the header_brigade when
193 the proxy loop is retried (ping), so I need to rework this.
194 Do you think we'd better remove the prefetch, or maybe just
195 make it nonblocking (by default)?
196 jim: Non-blocking seems the best way to handle...
198 * mod_dav: Allow other modules to become providers and add ACLs
199 to the DAV response. Requires a release of apr-util v1.6.
200 trunk patch: http://svn.apache.org/r1748322
201 2.4.x: trunk works modulo CHANGES/MMN
203 rpluem asks: Will this compile with apr-util < v1.6 and keep
204 mod_dav working (without the new features of the patch of course)?
205 I doubt that we will require apr-util 1.6 for the lifetime of 2.4.x
206 (see the discussion around ap_cstr_casecmp[n] an apr 1.6)
207 minfrin: Yes, as you can see in the patch everything applies only
208 if APR_XML_X2T_PARSED is defined, and the patch was tested with
209 both apr-util v1.6 and apr-util v1.5.
212 PATCHES/ISSUES THAT ARE STALLED
214 * core: Add ap_errorlog_provider to make ErrorLog logging modular. This
215 backport keeps syslog logging as part of httpd core and only adds
216 API to allow other modules to be used for error logging.
217 trunk patch: http://svn.apache.org/r1525597
218 http://svn.apache.org/r1525664
219 http://svn.apache.org/r1525845
220 http://svn.apache.org/r1527003
221 http://svn.apache.org/r1527005
222 http://svn.apache.org/r1532344
223 http://svn.apache.org/r1539988
224 http://svn.apache.org/r1541029
225 http://svn.apache.org/r1543979
226 http://svn.apache.org/r1544156
227 http://svn.apache.org/r1626978
228 2.4.x patch: http://people.apache.org/~jkaluza/patches/httpd-2.4.x-errorlog_provider.patch
230 +1: covener w/ doc or code to fix syntax (providername:providerarg not supported like syslog or socacheproviders,
231 needs 2 args which is not valid in ErrorLog manual)
232 trawick: nit: fix "writing" in "/* NULL if we are writting to syslog */"
233 (sorry, haven't finished reviewing completely)
234 jim: What is the status of this??
236 * mod_proxy: Add ap_proxy_define_match_worker() and use it for ProxyPassMatch
237 and ProxyMatch section to distinguish between normal workers and workers
238 with regex substitutions in the name. Implement handling of such workers
239 in ap_proxy_get_worker(). Fixes the bug when regex workers were not
240 matched and used for request. PR 43513.
241 trunk patch: http://svn.apache.org/r1609680
242 http://svn.apache.org/r1609688
243 http://svn.apache.org/r1641381
244 ylavic: Merge patch provided (reusing new->real to avoid double de_socketfy() call).
245 Also added missing r1609688 to the patchset.
246 2.4.x patch: http://people.apache.org/~ylavic/httpd-2.4.x-ap_proxy_define_match_worker.patch
248 -0: covener tried to review this one in Austin with Jeff. Does the added match function
249 really cover a very narrow set of parameters with the way it skips over backreferences?
250 Also, why a new API vs. just setting the field inline?
252 * mod_systemd: New module, for integration with systemd on Linux.
253 trunk patch: http://svn.apache.org/r1393976
254 http://svn.apache.org/r1393997
255 http://svn.apache.org/r1484554
256 http://svn.apache.org/r1528032
257 http://svn.apache.org/r1528034
258 http://svn.apache.org/r1614821
259 http://svn.apache.org/r1618579
260 http://svn.apache.org/r1618588
261 2.4.x patch: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-mod_systemd.patch
263 sf comments: The IdleShutdown logic seems broken. Consider a single
264 active connection that is stalled for 10 seconds. That
265 connection will be broken after GracefulShutdownTimeout.
266 A better logic would be to check if there is any open
267 connection that is not in keep-alive state.
269 * mod_journald: Add new module mod_journald to log error logs into journald.
270 This patch needs changes done in mod_systemd patch (already
272 trunk patch: http://svn.apache.org/r1610339
273 http://svn.apache.org/r1621806
274 2.4.x patch: http://people.apache.org/~jkaluza/patches/httpd-2.4.x-mod_journald.patch
276 rjung, minfrin: Not understanding "This patch needs changes done in
277 mod_systemd patch", am I right in understanding this patch is
279 jkaluza: No, that patch is not committed yet. It is in STALLED section.
280 The link for that patch is: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-mod_systemd.patch
282 * core: Add support for systemd socket activation.
283 trunk patch: http://svn.apache.org/r1511033
284 http://svn.apache.org/r1608686
285 http://svn.apache.org/r1608694
286 http://svn.apache.org/r1608703
287 http://svn.apache.org/r1608721
288 http://svn.apache.org/r1608744
289 2.4.x patch: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-socket-activation.patch
292 * mod_proxy: Ensure network errors detected by the proxy are returned as
293 504 Gateway Timout as opposed to 502 Bad Gateway
294 trunk patch: https://svn.apache.org/viewvc?view=revision&revision=1480058
295 2.4.x patch: trunk patch works modulo CHANGES
297 -1: rpluem: This change is still disputed. See
298 http://mail-archives.apache.org/mod_mbox/httpd-dev/201305.mbox/%3C1B16B9E3-87BA-4EEF-939C-7C7313B54714%40gbiv.com%3E
300 * cross-compile: allow to provide CC_FOR_BUILD so that gen_test_char will be
301 compiled by the build compiler instead of the host compiler.
302 Also set CC_FOR_BUILD to 'cc' when cross-compilation is detected.
303 Trunk patches: http://svn.apache.org/viewvc?view=revision&revision=1327907
304 http://svn.apache.org/viewvc?view=revision&revision=1328390
305 http://svn.apache.org/viewvc?view=revision&revision=1328714
306 2.4 patch: http://people.apache.org/~fuankg/diffs/httpd-2.4.x-cross_compile.diff
307 fuankg: on hold until we agree for a better and more simple solution ...
309 * Makefile.win: Added copying of .vbs / .wsf CGIs to Windows install target.
310 Moved fixing of shebang to separate target so that it is
311 no longer executed by default and all CGIs remain inactive.
312 trunk patch: http://svn.apache.org/viewvc?view=revision&revision=1387984
313 http://svn.apache.org/viewvc?view=revision&revision=1421203
314 http://svn.apache.org/viewvc?view=revision&revision=1421591
315 2.4.x patch: http://people.apache.org/~fuankg/diffs/httpd-2.4.x-Makefile.win.diff
318 This commit is essentially deciding that an httpd install on
319 Windows now has printenv/testcgi written in 2 more languages.
320 To the extent that the usefulness is that it shows how to make scripts
321 of these types executable by httpd, I believe that the documentation
322 is the proper place to solve that. To the extent that the usefullness
323 is to show how to implement a CGI in these particular languages, I believe
324 that the httpd distribution and documentation in general is not the
325 place for that. Historically these types of scripts have caused problems
326 for downstream vendorsas well as newbies (and sometimes the intersection
327 of those two groups) who don't understand that these are information leaks
328 once they are enabled, and the subtlety of the way they are disabled ("Apache
329 messed up the first line; let me fix that") contributes to that.
330 fuankg notes: I've just added a big warning to all CGI scripts which should now
331 make absolutely clear that these CGIs are for testing purpose only - so those
332 who enable those scripts with inserting the right shebang should be 100% aware
333 of any risks (this should cover your last point).
334 jim: trawick, does the above address your concerns?
335 trawick: to some extent (somebody reading the script gets an idea)
336 Why isn't the configuration requirement documented instead
337 of described indirectly in a sample?
338 Why are these new samples added to the install without three
339 votes? (I didn't veto it; put your name next to the two
340 existing ones and I'll be satisified that enough people
341 considered this addition as an appropriate solution for a
342 real httpd usability problem.)
343 wrowe: I'd agree with trawick, and suggest that these scripts can begin
344 their life somewhere in the manual/ tree. This really seems like
345 the place where /usr/share/httpd/examples/ would be useful, but
346 there isn't an ordinary directory for that. Since we want none
347 of the scripts to function 'out of the box', what about a new
348 cgi-examples/ dir alongside cgi-bin/? Otherwise manual/cgi/examples
351 * core: block Define and Undefine in vhost and directory context. Because
352 it is EXEC_ON_READ, it "breaks out" of these contexts anyway.
353 trunk patch: http://svn.apache.org/r1656063
354 http://svn.apache.org/r1656122
355 2.4.x patch: http://people.apache.org/~covener/patches/2.4.x-define-limits.diff
356 +1: covener (I need to review the docs manually in this area)
357 -1: wrowe (blocking will break "working" .conf files on a subversion update
358 meant to pick up security fixes. "Alerting" I would agree to.)