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