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.21 : In development.
38 2.4.20 : Tagged on April 4, 2016.
39 2.4.19 : Tagged on March 21, 2016, not released.
40 2.4.18 : Tagged on December 8, 2015. Released on December 14, 2015.
41 2.4.17 : Tagged on October 9, 2015. Released October 13, 2015.
42 2.4.16 : Tagged on July 9, 2015. Released July 15, 2015
43 2.4.15 : Tagged on June 19, 2015. Not released.
44 2.4.14 : Tagged on June 11, 2015. Not released.
45 2.4.13 : Tagged on June 4, 2015. Not released.
46 2.4.12 : Tagged on January 22, 2015. Released Jan 29, 2015
47 2.4.11 : Tagged on January 15, 2015. Not released.
48 2.4.10 : Tagged on July 15, 2014. Released July 21, 2014
49 2.4.9 : Tagged on March 13, 2014. Released on March 17, 2014
50 2.4.8 : Tagged on March 11, 2014. Not released.
51 2.4.7 : Tagged on November 19, 2013. Released on Nov 25, 2013
52 2.4.6 : Tagged on July 15, 2013. Released July, 22, 2013
53 2.4.5 : Tagged on July 11, 2013, not released.
54 2.4.4 : Tagged on February 18, 2013. Released Feb 25, 2013
55 2.4.3 : Tagged on August 17, 2012. Released Aug 18, 2012
56 2.4.2 : Tagged on April 5, 2012. Released Apr 17, 2012.
57 2.4.1 : Tagged on February 13, 2012. Released Feb 21, 2012.
58 2.4.0 : Tagged on January 16, 2012, not released.
59 2.3.16 : Tagged on December 15, 2011.
60 2.3.15 : Tagged on November 8, 2011. Released Nov. 15, 2011.
61 2.3.14 : Tagged on August 1, 2011. Released Aug. 9, 2011.
62 2.3.13 : Tagged on June 28, 2011, not released.
63 2.3.12 : Tagged on May 11, 2011. Released May 23, 2011.
64 2.3.11 : Released as Beta on March 7, 2011.
65 2.3.10 : Tagged on December 13, 2010. Released Dec 21, 2010.
66 2.3.9 : Tagged on November 23, 2010, not released.
67 2.3.8 : Tagged on August 24, 2010.
68 2.3.7 : Tagged on August 19, 2010, not released.
69 2.3.6 : Released on June 21, 2010.
70 2.3.5 : Released on January 26, 2010.
71 2.3.4 : Released on December 8, 2009.
72 2.3.3 : Tagged on November 11, 2009, not released.
73 2.3.2 : Tagged on March 23, 2009, not released.
74 2.3.1 : Tagged on January 2, 2009, not released.
75 2.3.0 : Tagged on December 6, 2008, not released.
77 Contributors looking for a mission:
79 * Just do an egrep on "TODO" or "XXX" in the source.
81 * Review the bug database at: http://issues.apache.org/bugzilla/
83 * Review the "PatchAvailable" bugs in the bug database:
85 https://issues.apache.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Apache+httpd-2&keywords=PatchAvailable
87 After testing, you can append a comment saying "Reviewed and tested".
89 * Open bugs in the bug database.
91 * See also the STATUS file in the docs/ directory, which lists documentation-specific TODO items.
94 CURRENT RELEASE NOTES:
96 * Forward binary compatibility is expected of Apache 2.4.x releases, such
97 that no MMN major number changes will occur after 2.4.1. Such changes can
98 only be made in the trunk.
100 * All commits to branches/2.4.x must be reflected in SVN trunk,
101 as well, if they apply. Logical progression is commit to trunk
102 then merge into branches/2.4.x, as applicable.
104 * Current exceptions for RTC for this branch:
109 . non-Unix, single-platform code
111 RELEASE SHOWSTOPPERS:
114 PATCHES ACCEPTED TO BACKPORT FROM TRUNK:
115 [ start all new proposals below, under PATCHES PROPOSED. ]
118 PATCHES PROPOSED TO BACKPORT FROM TRUNK:
119 [ New proposals should be added at the end of the list ]
121 *) mod_proxy_hcheck: Dynamic reverse proxy backend health check module
122 Trunk version of patch: <various>
123 Backport version for 2.4.x of patch:
124 http://home.apache.org/~jim/patches/hcheck-2.4-v3.patch
128 *) mod_ssl: Add "no_crl_for_cert_ok" flag to SSLCARevocationCheck directive
129 to opt-in previous behaviour (2.2) with CRLs verification when checking
130 certificate(s) with no corresponding CRL.
131 trunk patch: http://svn.apache.org/r1734561
132 http://svn.apache.org/r1734807
133 http://svn.apache.org/r1735159
134 http://svn.apache.org/r1735337
135 http://svn.apache.org/r1737265
136 2.4.x patch: trunk works (modulo CHANGES) or
137 http://home.apache.org/~ylavic/patches/httpd-2.4.x-no_crl_for_cert_ok-v2.patch
140 *) mod_proxy_http2: add http2 proxy support in new, experimental module.
141 Includes backport of r1729208 to set ALPN protocols for ssl backend
143 Trunk version of patch: <various>
144 Backport version for 2.4.x of patch: https://www.eissing.org/proxy_http2_2.4v4.patch
146 updated patch after review by cjaillet, merged 1735668,1735748 from trunk
147 updated patch with APLOGNOs by merging 1735931,1735935 from trunk
148 updated patch with APLOGNOs by merging 1735942 from trunk
150 *) CGIVar for controlling building of REQUEST_URI (and future uses)
151 As mentioned on dev@:
152 * This is intended to replace existing methods of configuring how various
153 CGI vars should be built over the long term, though only REQUEST_URI is
155 * If the mechanism should be usable by third-party modules for its own
156 concerns, a check for recognized-envvar can be removed from the command
157 processor and the rest of the code will let the third-party module do
158 the right thing since the rule for a var is a character string in a table,
159 not a separate core_dir_config flag with enumerated values.
160 Trunk patch: r1734947, 1735952
161 2.4.x patch: https://emptyhammock.com/media/downloads/CGIVar-to-2.4.x.txt
162 Bad Jeff: The MMN change was missing originally, same patch updated :(
165 *) mod_ssl: Return 502 instead of 500 when SSL peer check or
166 proxy_post_handshake hook fails.
167 Trunk patch: r1645529 (works)
168 2.4.x patch which adds CHANGES: https://emptyhammock.com/media/downloads/r1645529-to-2.4.x.txt
170 ylavic: there may be missing bits, see thread for commit r1736510.
172 *) mod_include: add the <!--#comment ...> syntax in order to include comments
174 Trunk patch: http://svn.apache.org/r1737476
175 2.4.x patch: trunk patch works (compatibility note to be adjusted)
178 PATCHES/ISSUES THAT ARE BEING WORKED
180 *) http: Don't remove the Content-Length of zero from a HEAD response if
181 it comes from an origin server, module or script. Allow the previous
182 behaviour (for legacy/buggy modules only, not origin) by also backporting
183 the HttpContentLengthHeadZero directive (and also HttpExpectStrict which
184 comes for free with the same commit).
185 trunk patch: http://svn.apache.org/r1554303
186 http://svn.apache.org/r1678215
187 2.4.x patch: http://people.apache.org/~ylavic/httpd-2.4.x-preserve_head_cl_zero.patch
189 ylavic: r1554303 issued a major MMN bump, but since the ABI change is two
190 ints added at the end of core_server_config, the proposed merge
191 does a minor bump only.
192 minfrin: Two new directives need to be documented.
194 * mod_proxy_http: Don't establish or reuse a backend connection before pre-
195 fetching the request body, so to minimize the delay between it is supposed
196 to be alive and the first bytes sent: this is a best effort to prevent the
197 backend from closing because of idle or keepalive timeout in the meantime.
198 Also, handle a new "proxy-flushall" environment variable which allows to
199 flush any forwarded body data immediately. PR 56541+37920.
200 trunk patch: http://svn.apache.org/r1656259
201 http://svn.apache.org/r1656359 (CHANGES entry)
202 2.4.x patch: trunk works (modulo CHANGES, docs/log-message-tags)
204 -0: jim: This seems to be a hit to normal performance, to handle an
205 error and/or non-normal condition. The pre-fetch is
206 expensive, and is always done, even before we know that
207 the backend is available to rec' it. I understand the
208 error described, but is the fix actually worth it (plus
209 it seems to allow for a DDoS vector).
210 ylavic: It seems to me that the problem is real since we reuse the
211 connection before prefetching 16K (either controlled by the
212 client, or by an input filter), we currently always prefetch
213 these bytes already. Regarding performance I don't see any
214 difference (more cycles) compared with the current code.
215 However I think I failed to rebuild the header_brigade when
216 the proxy loop is retried (ping), so I need to rework this.
217 Do you think we'd better remove the prefetch, or maybe just
218 make it nonblocking (by default)?
219 jim: Non-blocking seems the best way to handle...
222 PATCHES/ISSUES THAT ARE STALLED
224 * core: Add ap_errorlog_provider to make ErrorLog logging modular. This
225 backport keeps syslog logging as part of httpd core and only adds
226 API to allow other modules to be used for error logging.
227 trunk patch: http://svn.apache.org/r1525597
228 http://svn.apache.org/r1525664
229 http://svn.apache.org/r1525845
230 http://svn.apache.org/r1527003
231 http://svn.apache.org/r1527005
232 http://svn.apache.org/r1532344
233 http://svn.apache.org/r1539988
234 http://svn.apache.org/r1541029
235 http://svn.apache.org/r1543979
236 http://svn.apache.org/r1544156
237 http://svn.apache.org/r1626978
238 2.4.x patch: http://people.apache.org/~jkaluza/patches/httpd-2.4.x-errorlog_provider.patch
240 +1: covener w/ doc or code to fix syntax (providername:providerarg not supported like syslog or socacheproviders,
241 needs 2 args which is not valid in ErrorLog manual)
242 trawick: nit: fix "writing" in "/* NULL if we are writting to syslog */"
243 (sorry, haven't finished reviewing completely)
244 jim: What is the status of this??
246 * mod_proxy: Add ap_proxy_define_match_worker() and use it for ProxyPassMatch
247 and ProxyMatch section to distinguish between normal workers and workers
248 with regex substitutions in the name. Implement handling of such workers
249 in ap_proxy_get_worker(). Fixes the bug when regex workers were not
250 matched and used for request. PR 43513.
251 trunk patch: http://svn.apache.org/r1609680
252 http://svn.apache.org/r1609688
253 http://svn.apache.org/r1641381
254 ylavic: Merge patch provided (reusing new->real to avoid double de_socketfy() call).
255 Also added missing r1609688 to the patchset.
256 2.4.x patch: http://people.apache.org/~ylavic/httpd-2.4.x-ap_proxy_define_match_worker.patch
258 -0: covener tried to review this one in Austin with Jeff. Does the added match function
259 really cover a very narrow set of parameters with the way it skips over backreferences?
260 Also, why a new API vs. just setting the field inline?
262 * mod_systemd: New module, for integration with systemd on Linux.
263 trunk patch: http://svn.apache.org/r1393976
264 http://svn.apache.org/r1393997
265 http://svn.apache.org/r1484554
266 http://svn.apache.org/r1528032
267 http://svn.apache.org/r1528034
268 http://svn.apache.org/r1614821
269 http://svn.apache.org/r1618579
270 http://svn.apache.org/r1618588
271 2.4.x patch: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-mod_systemd.patch
273 sf comments: The IdleShutdown logic seems broken. Consider a single
274 active connection that is stalled for 10 seconds. That
275 connection will be broken after GracefulShutdownTimeout.
276 A better logic would be to check if there is any open
277 connection that is not in keep-alive state.
279 * mod_journald: Add new module mod_journald to log error logs into journald.
280 This patch needs changes done in mod_systemd patch (already
282 trunk patch: http://svn.apache.org/r1610339
283 http://svn.apache.org/r1621806
284 2.4.x patch: http://people.apache.org/~jkaluza/patches/httpd-2.4.x-mod_journald.patch
286 rjung, minfrin: Not understanding "This patch needs changes done in
287 mod_systemd patch", am I right in understanding this patch is
289 jkaluza: No, that patch is not committed yet. It is in STALLED section.
290 The link for that patch is: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-mod_systemd.patch
292 * core: Add support for systemd socket activation.
293 trunk patch: http://svn.apache.org/r1511033
294 http://svn.apache.org/r1608686
295 http://svn.apache.org/r1608694
296 http://svn.apache.org/r1608703
297 http://svn.apache.org/r1608721
298 http://svn.apache.org/r1608744
299 2.4.x patch: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-socket-activation.patch
302 * mod_proxy: Ensure network errors detected by the proxy are returned as
303 504 Gateway Timout as opposed to 502 Bad Gateway
304 trunk patch: https://svn.apache.org/viewvc?view=revision&revision=1480058
305 2.4.x patch: trunk patch works modulo CHANGES
307 -1: rpluem: This change is still disputed. See
308 http://mail-archives.apache.org/mod_mbox/httpd-dev/201305.mbox/%3C1B16B9E3-87BA-4EEF-939C-7C7313B54714%40gbiv.com%3E
310 * cross-compile: allow to provide CC_FOR_BUILD so that gen_test_char will be
311 compiled by the build compiler instead of the host compiler.
312 Also set CC_FOR_BUILD to 'cc' when cross-compilation is detected.
313 Trunk patches: http://svn.apache.org/viewvc?view=revision&revision=1327907
314 http://svn.apache.org/viewvc?view=revision&revision=1328390
315 http://svn.apache.org/viewvc?view=revision&revision=1328714
316 2.4 patch: http://people.apache.org/~fuankg/diffs/httpd-2.4.x-cross_compile.diff
317 fuankg: on hold until we agree for a better and more simple solution ...
319 * Makefile.win: Added copying of .vbs / .wsf CGIs to Windows install target.
320 Moved fixing of shebang to separate target so that it is
321 no longer executed by default and all CGIs remain inactive.
322 trunk patch: http://svn.apache.org/viewvc?view=revision&revision=1387984
323 http://svn.apache.org/viewvc?view=revision&revision=1421203
324 http://svn.apache.org/viewvc?view=revision&revision=1421591
325 2.4.x patch: http://people.apache.org/~fuankg/diffs/httpd-2.4.x-Makefile.win.diff
328 This commit is essentially deciding that an httpd install on
329 Windows now has printenv/testcgi written in 2 more languages.
330 To the extent that the usefulness is that it shows how to make scripts
331 of these types executable by httpd, I believe that the documentation
332 is the proper place to solve that. To the extent that the usefullness
333 is to show how to implement a CGI in these particular languages, I believe
334 that the httpd distribution and documentation in general is not the
335 place for that. Historically these types of scripts have caused problems
336 for downstream vendorsas well as newbies (and sometimes the intersection
337 of those two groups) who don't understand that these are information leaks
338 once they are enabled, and the subtlety of the way they are disabled ("Apache
339 messed up the first line; let me fix that") contributes to that.
340 fuankg notes: I've just added a big warning to all CGI scripts which should now
341 make absolutely clear that these CGIs are for testing purpose only - so those
342 who enable those scripts with inserting the right shebang should be 100% aware
343 of any risks (this should cover your last point).
344 jim: trawick, does the above address your concerns?
345 trawick: to some extent (somebody reading the script gets an idea)
346 Why isn't the configuration requirement documented instead
347 of described indirectly in a sample?
348 Why are these new samples added to the install without three
349 votes? (I didn't veto it; put your name next to the two
350 existing ones and I'll be satisified that enough people
351 considered this addition as an appropriate solution for a
352 real httpd usability problem.)
353 wrowe: I'd agree with trawick, and suggest that these scripts can begin
354 their life somewhere in the manual/ tree. This really seems like
355 the place where /usr/share/httpd/examples/ would be useful, but
356 there isn't an ordinary directory for that. Since we want none
357 of the scripts to function 'out of the box', what about a new
358 cgi-examples/ dir alongside cgi-bin/? Otherwise manual/cgi/examples