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.24 : In development.
38 2.4.23 : Tagged on June 30, 2016. Released on July 05, 2016.
39 2.4.22 : Tagged on June 20, 2016, not released.
40 2.4.21 : Tagged on June 16, 2016, not released.
41 2.4.20 : Tagged on April 4, 2016. Released on April 11, 2016.
42 2.4.19 : Tagged on March 21, 2016, not released.
43 2.4.18 : Tagged on December 8, 2015. Released on December 14, 2015.
44 2.4.17 : Tagged on October 9, 2015. Released October 13, 2015.
45 2.4.16 : Tagged on July 9, 2015. Released July 15, 2015
46 2.4.15 : Tagged on June 19, 2015. Not released.
47 2.4.14 : Tagged on June 11, 2015. Not released.
48 2.4.13 : Tagged on June 4, 2015. Not released.
49 2.4.12 : Tagged on January 22, 2015. Released Jan 29, 2015
50 2.4.11 : Tagged on January 15, 2015. Not released.
51 2.4.10 : Tagged on July 15, 2014. Released July 21, 2014
52 2.4.9 : Tagged on March 13, 2014. Released on March 17, 2014
53 2.4.8 : Tagged on March 11, 2014. Not released.
54 2.4.7 : Tagged on November 19, 2013. Released on Nov 25, 2013
55 2.4.6 : Tagged on July 15, 2013. Released July, 22, 2013
56 2.4.5 : Tagged on July 11, 2013, not released.
57 2.4.4 : Tagged on February 18, 2013. Released Feb 25, 2013
58 2.4.3 : Tagged on August 17, 2012. Released Aug 18, 2012
59 2.4.2 : Tagged on April 5, 2012. Released Apr 17, 2012.
60 2.4.1 : Tagged on February 13, 2012. Released Feb 21, 2012.
61 2.4.0 : Tagged on January 16, 2012, not released.
62 2.3.16 : Tagged on December 15, 2011.
63 2.3.15 : Tagged on November 8, 2011. Released Nov. 15, 2011.
64 2.3.14 : Tagged on August 1, 2011. Released Aug. 9, 2011.
65 2.3.13 : Tagged on June 28, 2011, not released.
66 2.3.12 : Tagged on May 11, 2011. Released May 23, 2011.
67 2.3.11 : Released as Beta on March 7, 2011.
68 2.3.10 : Tagged on December 13, 2010. Released Dec 21, 2010.
69 2.3.9 : Tagged on November 23, 2010, not released.
70 2.3.8 : Tagged on August 24, 2010.
71 2.3.7 : Tagged on August 19, 2010, not released.
72 2.3.6 : Released on June 21, 2010.
73 2.3.5 : Released on January 26, 2010.
74 2.3.4 : Released on December 8, 2009.
75 2.3.3 : Tagged on November 11, 2009, not released.
76 2.3.2 : Tagged on March 23, 2009, not released.
77 2.3.1 : Tagged on January 2, 2009, not released.
78 2.3.0 : Tagged on December 6, 2008, not released.
80 Contributors looking for a mission:
82 * Just do an egrep on "TODO" or "XXX" in the source.
84 * Review the bug database at: http://issues.apache.org/bugzilla/
86 * Review the "PatchAvailable" bugs in the bug database:
88 https://issues.apache.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Apache+httpd-2&keywords=PatchAvailable
90 After testing, you can append a comment saying "Reviewed and tested".
92 * Open bugs in the bug database.
94 * See also the STATUS file in the docs/ directory, which lists documentation-specific TODO items.
97 CURRENT RELEASE NOTES:
99 * Forward binary compatibility is expected of Apache 2.4.x releases, such
100 that no MMN major number changes will occur after 2.4.1. Such changes can
101 only be made in the trunk.
103 * All commits to branches/2.4.x must be reflected in SVN trunk,
104 as well, if they apply. Logical progression is commit to trunk
105 then merge into branches/2.4.x, as applicable.
107 * Current exceptions for RTC for this branch:
112 . non-Unix, single-platform code
114 RELEASE SHOWSTOPPERS:
117 PATCHES ACCEPTED TO BACKPORT FROM TRUNK:
118 [ 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 Warn the users about Last-Modified header value replacements and
147 improved handling of non-GMT datestr.
148 trunk patch: http://svn.apache.org/r1748379
149 http://svn.apache.org/r1750747
150 http://svn.apache.org/r1750749
151 http://svn.apache.org/r1750953
152 http://svn.apache.org/r1751138
153 2.4.x: trunk patch works. The last revision has been discussed
154 in dev@ and submitted by Yann. Tested the code with a simple PHP
155 script returning different Last-Modified headers (GMT now,
156 GMT now Europe/Paris, GMT tomorrow).
159 *) ab: Set the Server Name Indication (SNI) extension on outgoing TLS
160 connections (unless -I is specified), according to the Host header (if
161 any) or the requested URL's hostname otherwise.
162 trunk patch: http://svn.apache.org/r1750854
163 http://svn.apache.org/r1750855
164 http://svn.apache.org/r1750947
165 http://svn.apache.org/r1750955
166 http://svn.apache.org/r1750960
167 2.4.x patch: http://home.apache.org/~ylavic/patches/httpd-2.4.x-ab_sni.patch
168 (needed to adapt CHANGES entry since r1750854)
171 *) mod_proxy_fcgi: Fix 2.4.23 breakage for mod_rewrite per-dir and query
172 string showing up in SCRIPT_FILENAME. PR59815
173 trunk patch: http://svn.apache.org/r1751970
174 2.4.x patch: trunk works + CHANGES
177 *) CMake: fix various issues for Windows/Visual Studio build environments.
179 trunk patch: http://svn.apache.org/r1752331
180 http://svn.apache.org/r1752332
181 http://svn.apache.org/r1752333
184 *) mod_proxy_fcgi: read the whole FCGI response even when the content has
185 not been modified (HTTP 304) to avoid subsequent bougus reads and
186 confusing error messages logged.
187 trunk patch: http://svn.apache.org/r1752347
188 2.4.x patch: trunk works
192 PATCHES/ISSUES THAT ARE BEING WORKED
194 *) http: Don't remove the Content-Length of zero from a HEAD response if
195 it comes from an origin server, module or script. Allow the previous
196 behaviour (for legacy/buggy modules only, not origin) by also backporting
197 the HttpContentLengthHeadZero directive (and also HttpExpectStrict which
198 comes for free with the same commit).
199 trunk patch: http://svn.apache.org/r1554303
200 http://svn.apache.org/r1678215
201 2.4.x patch: http://people.apache.org/~ylavic/httpd-2.4.x-preserve_head_cl_zero.patch
203 ylavic: r1554303 issued a major MMN bump, but since the ABI change is two
204 ints added at the end of core_server_config, the proposed merge
205 does a minor bump only.
206 minfrin: Two new directives need to be documented.
208 * mod_proxy_http: Don't establish or reuse a backend connection before pre-
209 fetching the request body, so to minimize the delay between it is supposed
210 to be alive and the first bytes sent: this is a best effort to prevent the
211 backend from closing because of idle or keepalive timeout in the meantime.
212 Also, handle a new "proxy-flushall" environment variable which allows to
213 flush any forwarded body data immediately. PR 56541+37920.
214 trunk patch: http://svn.apache.org/r1656259
215 http://svn.apache.org/r1656359 (CHANGES entry)
216 2.4.x patch: trunk works (modulo CHANGES, docs/log-message-tags)
218 -0: jim: This seems to be a hit to normal performance, to handle an
219 error and/or non-normal condition. The pre-fetch is
220 expensive, and is always done, even before we know that
221 the backend is available to rec' it. I understand the
222 error described, but is the fix actually worth it (plus
223 it seems to allow for a DDoS vector).
224 ylavic: It seems to me that the problem is real since we reuse the
225 connection before prefetching 16K (either controlled by the
226 client, or by an input filter), we currently always prefetch
227 these bytes already. Regarding performance I don't see any
228 difference (more cycles) compared with the current code.
229 However I think I failed to rebuild the header_brigade when
230 the proxy loop is retried (ping), so I need to rework this.
231 Do you think we'd better remove the prefetch, or maybe just
232 make it nonblocking (by default)?
233 jim: Non-blocking seems the best way to handle...
235 * mod_dav: Allow other modules to become providers and add ACLs
236 to the DAV response. Requires a release of apr-util v1.6.
237 trunk patch: http://svn.apache.org/r1748322
238 2.4.x: trunk works modulo CHANGES/MMN
240 rpluem asks: Will this compile with apr-util < v1.6 and keep
241 mod_dav working (without the new features of the patch of course)?
242 I doubt that we will require apr-util 1.6 for the lifetime of 2.4.x
243 (see the discussion around ap_cstr_casecmp[n] an apr 1.6)
244 minfrin: Yes, as you can see in the patch everything applies only
245 if APR_XML_X2T_PARSED is defined, and the patch was tested with
246 both apr-util v1.6 and apr-util v1.5.
248 PATCHES/ISSUES THAT ARE STALLED
250 * core: Add ap_errorlog_provider to make ErrorLog logging modular. This
251 backport keeps syslog logging as part of httpd core and only adds
252 API to allow other modules to be used for error logging.
253 trunk patch: http://svn.apache.org/r1525597
254 http://svn.apache.org/r1525664
255 http://svn.apache.org/r1525845
256 http://svn.apache.org/r1527003
257 http://svn.apache.org/r1527005
258 http://svn.apache.org/r1532344
259 http://svn.apache.org/r1539988
260 http://svn.apache.org/r1541029
261 http://svn.apache.org/r1543979
262 http://svn.apache.org/r1544156
263 http://svn.apache.org/r1626978
264 2.4.x patch: http://people.apache.org/~jkaluza/patches/httpd-2.4.x-errorlog_provider.patch
266 +1: covener w/ doc or code to fix syntax (providername:providerarg not supported like syslog or socacheproviders,
267 needs 2 args which is not valid in ErrorLog manual)
268 trawick: nit: fix "writing" in "/* NULL if we are writting to syslog */"
269 (sorry, haven't finished reviewing completely)
270 jim: What is the status of this??
272 * mod_proxy: Add ap_proxy_define_match_worker() and use it for ProxyPassMatch
273 and ProxyMatch section to distinguish between normal workers and workers
274 with regex substitutions in the name. Implement handling of such workers
275 in ap_proxy_get_worker(). Fixes the bug when regex workers were not
276 matched and used for request. PR 43513.
277 trunk patch: http://svn.apache.org/r1609680
278 http://svn.apache.org/r1609688
279 http://svn.apache.org/r1641381
280 ylavic: Merge patch provided (reusing new->real to avoid double de_socketfy() call).
281 Also added missing r1609688 to the patchset.
282 2.4.x patch: http://people.apache.org/~ylavic/httpd-2.4.x-ap_proxy_define_match_worker.patch
284 -0: covener tried to review this one in Austin with Jeff. Does the added match function
285 really cover a very narrow set of parameters with the way it skips over backreferences?
286 Also, why a new API vs. just setting the field inline?
288 * mod_systemd: New module, for integration with systemd on Linux.
289 trunk patch: http://svn.apache.org/r1393976
290 http://svn.apache.org/r1393997
291 http://svn.apache.org/r1484554
292 http://svn.apache.org/r1528032
293 http://svn.apache.org/r1528034
294 http://svn.apache.org/r1614821
295 http://svn.apache.org/r1618579
296 http://svn.apache.org/r1618588
297 2.4.x patch: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-mod_systemd.patch
299 sf comments: The IdleShutdown logic seems broken. Consider a single
300 active connection that is stalled for 10 seconds. That
301 connection will be broken after GracefulShutdownTimeout.
302 A better logic would be to check if there is any open
303 connection that is not in keep-alive state.
305 * mod_journald: Add new module mod_journald to log error logs into journald.
306 This patch needs changes done in mod_systemd patch (already
308 trunk patch: http://svn.apache.org/r1610339
309 http://svn.apache.org/r1621806
310 2.4.x patch: http://people.apache.org/~jkaluza/patches/httpd-2.4.x-mod_journald.patch
312 rjung, minfrin: Not understanding "This patch needs changes done in
313 mod_systemd patch", am I right in understanding this patch is
315 jkaluza: No, that patch is not committed yet. It is in STALLED section.
316 The link for that patch is: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-mod_systemd.patch
318 * core: Add support for systemd socket activation.
319 trunk patch: http://svn.apache.org/r1511033
320 http://svn.apache.org/r1608686
321 http://svn.apache.org/r1608694
322 http://svn.apache.org/r1608703
323 http://svn.apache.org/r1608721
324 http://svn.apache.org/r1608744
325 2.4.x patch: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-socket-activation.patch
328 * mod_proxy: Ensure network errors detected by the proxy are returned as
329 504 Gateway Timout as opposed to 502 Bad Gateway
330 trunk patch: https://svn.apache.org/viewvc?view=revision&revision=1480058
331 2.4.x patch: trunk patch works modulo CHANGES
333 -1: rpluem: This change is still disputed. See
334 http://mail-archives.apache.org/mod_mbox/httpd-dev/201305.mbox/%3C1B16B9E3-87BA-4EEF-939C-7C7313B54714%40gbiv.com%3E
336 * cross-compile: allow to provide CC_FOR_BUILD so that gen_test_char will be
337 compiled by the build compiler instead of the host compiler.
338 Also set CC_FOR_BUILD to 'cc' when cross-compilation is detected.
339 Trunk patches: http://svn.apache.org/viewvc?view=revision&revision=1327907
340 http://svn.apache.org/viewvc?view=revision&revision=1328390
341 http://svn.apache.org/viewvc?view=revision&revision=1328714
342 2.4 patch: http://people.apache.org/~fuankg/diffs/httpd-2.4.x-cross_compile.diff
343 fuankg: on hold until we agree for a better and more simple solution ...
345 * Makefile.win: Added copying of .vbs / .wsf CGIs to Windows install target.
346 Moved fixing of shebang to separate target so that it is
347 no longer executed by default and all CGIs remain inactive.
348 trunk patch: http://svn.apache.org/viewvc?view=revision&revision=1387984
349 http://svn.apache.org/viewvc?view=revision&revision=1421203
350 http://svn.apache.org/viewvc?view=revision&revision=1421591
351 2.4.x patch: http://people.apache.org/~fuankg/diffs/httpd-2.4.x-Makefile.win.diff
354 This commit is essentially deciding that an httpd install on
355 Windows now has printenv/testcgi written in 2 more languages.
356 To the extent that the usefulness is that it shows how to make scripts
357 of these types executable by httpd, I believe that the documentation
358 is the proper place to solve that. To the extent that the usefullness
359 is to show how to implement a CGI in these particular languages, I believe
360 that the httpd distribution and documentation in general is not the
361 place for that. Historically these types of scripts have caused problems
362 for downstream vendorsas well as newbies (and sometimes the intersection
363 of those two groups) who don't understand that these are information leaks
364 once they are enabled, and the subtlety of the way they are disabled ("Apache
365 messed up the first line; let me fix that") contributes to that.
366 fuankg notes: I've just added a big warning to all CGI scripts which should now
367 make absolutely clear that these CGIs are for testing purpose only - so those
368 who enable those scripts with inserting the right shebang should be 100% aware
369 of any risks (this should cover your last point).
370 jim: trawick, does the above address your concerns?
371 trawick: to some extent (somebody reading the script gets an idea)
372 Why isn't the configuration requirement documented instead
373 of described indirectly in a sample?
374 Why are these new samples added to the install without three
375 votes? (I didn't veto it; put your name next to the two
376 existing ones and I'll be satisified that enough people
377 considered this addition as an appropriate solution for a
378 real httpd usability problem.)
379 wrowe: I'd agree with trawick, and suggest that these scripts can begin
380 their life somewhere in the manual/ tree. This really seems like
381 the place where /usr/share/httpd/examples/ would be useful, but
382 there isn't an ordinary directory for that. Since we want none
383 of the scripts to function 'out of the box', what about a new
384 cgi-examples/ dir alongside cgi-bin/? Otherwise manual/cgi/examples
387 * core: block Define and Undefine in vhost and directory context. Because
388 it is EXEC_ON_READ, it "breaks out" of these contexts anyway.
389 trunk patch: http://svn.apache.org/r1656063
390 http://svn.apache.org/r1656122
391 2.4.x patch: http://people.apache.org/~covener/patches/2.4.x-define-limits.diff
392 +1: covener (I need to review the docs manually in this area)
393 -1: wrowe (blocking will break "working" .conf files on a subversion update
394 meant to pick up security fixes. "Alerting" I would agree to.)