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. Jim proposes to T&R ~ Dec 15th.
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:
119 PATCHES ACCEPTED TO BACKPORT FROM TRUNK:
120 [ start all new proposals below, under PATCHES PROPOSED. ]
123 PATCHES PROPOSED TO BACKPORT FROM TRUNK:
124 [ New proposals should be added at the end of the list ]
126 *) mod_proxy, mod_ssl: Handle SSLProxy* directives in <Proxy> sections,
127 allowing per backend TLS configuration.
128 trunk patch: http://svn.apache.org/r1740928
129 http://svn.apache.org/r1740960
130 http://svn.apache.org/r1740967
131 http://svn.apache.org/r1740987
132 http://svn.apache.org/r1740998
133 http://svn.apache.org/r1742697
134 http://svn.apache.org/r1756976
135 2.4.x patch: http://home.apache.org/~ylavic/patches/httpd-2.4.x-r1740928_and_co.patch
138 *) Follow up on check_headers() (r1773995) to restore EOC semantic.
139 trunk patch: http://svn.apache.org/r1774286
140 2.4.x patch: trunk works
143 *) Limit some kinds of rewrite looping. PR60478
144 trunk patch: http://svn.apache.org/r1774288.
145 2.4.x patch: trunk works
148 PATCHES/ISSUES THAT ARE BEING WORKED
149 [ New entried should be added at the START of the list ]
151 *) mod_ssl: Return 502 instead of 500 when SSL peer check or
152 proxy_post_handshake hook fails.
153 Trunk patch: r1645529 (works)
154 2.4.x patch which adds CHANGES: https://emptyhammock.com/media/downloads/r1645529-to-2.4.x.txt
156 ylavic: there may be missing bits, see thread for commit r1736510.
158 *) core: Drop an invalid Last-Modified header value coming
159 from a (F)CGI script instead of replacing it with Unix epoch.
160 Warn the users about Last-Modified header value replacements
161 and violations of the RFC.
162 trunk patch: http://svn.apache.org/r1748379
163 http://svn.apache.org/r1750747
164 http://svn.apache.org/r1750749
165 http://svn.apache.org/r1750953
166 http://svn.apache.org/r1751138
167 http://svn.apache.org/r1751139
168 http://svn.apache.org/r1751147
169 http://svn.apache.org/r1757818
170 2.4.x: trunk patches work, final view:
171 http://home.apache.org/~elukey/httpd-2.4.x-core-last_modified_tz_logging.patch
172 The problem has been discussed in dev@ extensively but we did not reach a common
173 agreement about how to proceed in the long term. While we wait, I would really like
174 to introduce useful logs for the users (the starting point of this change was a users@
175 email thread). If this is not the right way to go I will move the patch to other
176 sections of STATUS (stalled or being worked).
177 The code has been tested with a simple PHP script returning different Last-Modified
178 headers (GMT now, GMT now Europe/Paris, GMT tomorrow, GMT yesterday, PST now).
181 *) http: Don't remove the Content-Length of zero from a HEAD response if
182 it comes from an origin server, module or script. Allow the previous
183 behaviour (for legacy/buggy modules only, not origin) by also backporting
184 the HttpContentLengthHeadZero directive (and also HttpExpectStrict which
185 comes for free with the same commit).
186 trunk patch: http://svn.apache.org/r1554303
187 http://svn.apache.org/r1678215
188 2.4.x patch: http://people.apache.org/~ylavic/httpd-2.4.x-preserve_head_cl_zero.patch
190 ylavic: r1554303 issued a major MMN bump, but since the ABI change is two
191 ints added at the end of core_server_config, the proposed merge
192 does a minor bump only.
193 minfrin: Two new directives need to be documented.
195 * mod_proxy_http: Don't establish or reuse a backend connection before pre-
196 fetching the request body, so to minimize the delay between it is supposed
197 to be alive and the first bytes sent: this is a best effort to prevent the
198 backend from closing because of idle or keepalive timeout in the meantime.
199 Also, handle a new "proxy-flushall" environment variable which allows to
200 flush any forwarded body data immediately. PR 56541+37920.
201 trunk patch: http://svn.apache.org/r1656259
202 http://svn.apache.org/r1656359 (CHANGES entry)
203 2.4.x patch: trunk works (modulo CHANGES, docs/log-message-tags)
205 -0: jim: This seems to be a hit to normal performance, to handle an
206 error and/or non-normal condition. The pre-fetch is
207 expensive, and is always done, even before we know that
208 the backend is available to rec' it. I understand the
209 error described, but is the fix actually worth it (plus
210 it seems to allow for a DDoS vector).
211 ylavic: It seems to me that the problem is real since we reuse the
212 connection before prefetching 16K (either controlled by the
213 client, or by an input filter), we currently always prefetch
214 these bytes already. Regarding performance I don't see any
215 difference (more cycles) compared with the current code.
216 However I think I failed to rebuild the header_brigade when
217 the proxy loop is retried (ping), so I need to rework this.
218 Do you think we'd better remove the prefetch, or maybe just
219 make it nonblocking (by default)?
220 jim: Non-blocking seems the best way to handle...
222 * mod_dav: Allow other modules to become providers and add ACLs
223 to the DAV response. Requires a release of apr-util v1.6.
224 trunk patch: http://svn.apache.org/r1748322
225 2.4.x: trunk works modulo CHANGES/MMN
227 rpluem asks: Will this compile with apr-util < v1.6 and keep
228 mod_dav working (without the new features of the patch of course)?
229 I doubt that we will require apr-util 1.6 for the lifetime of 2.4.x
230 (see the discussion around ap_cstr_casecmp[n] an apr 1.6)
231 minfrin: Yes, as you can see in the patch everything applies only
232 if APR_XML_X2T_PARSED is defined, and the patch was tested with
233 both apr-util v1.6 and apr-util v1.5.
234 -1: jorton, breaks binary backwards compat per dev@ discuss
235 msgid <20160902120654.GA12674@redhat.com>
236 (& also, making the structure change with apr-util version
237 means it breaks binary compat across an apr-util upgrade?)
239 * mod_auth_digest: Reduce severity from NOTICE to DEBUG this
240 once-per-restart msg (I guess the concern was that the RNG
241 could block after this message)
243 AH01757: generating secret for digest authentication ...
245 trunk patch: This was fixed in trunk as a trivial part of http://svn.apache.org/r1492395
246 2.4.x patch: Just change the loglevel to DEBUG.
249 PATCHES/ISSUES THAT ARE STALLED
251 * core: Add ap_errorlog_provider to make ErrorLog logging modular. This
252 backport keeps syslog logging as part of httpd core and only adds
253 API to allow other modules to be used for error logging.
254 trunk patch: http://svn.apache.org/r1525597
255 http://svn.apache.org/r1525664
256 http://svn.apache.org/r1525845
257 http://svn.apache.org/r1527003
258 http://svn.apache.org/r1527005
259 http://svn.apache.org/r1532344
260 http://svn.apache.org/r1539988
261 http://svn.apache.org/r1541029
262 http://svn.apache.org/r1543979
263 http://svn.apache.org/r1544156
264 http://svn.apache.org/r1626978
265 2.4.x patch: http://people.apache.org/~jkaluza/patches/httpd-2.4.x-errorlog_provider.patch
267 +1: covener w/ doc or code to fix syntax (providername:providerarg not supported like syslog or socacheproviders,
268 needs 2 args which is not valid in ErrorLog manual)
269 trawick: nit: fix "writing" in "/* NULL if we are writing to syslog */"
270 (sorry, haven't finished reviewing completely)
271 jim: What is the status of this??
273 * mod_proxy: Add ap_proxy_define_match_worker() and use it for ProxyPassMatch
274 and ProxyMatch section to distinguish between normal workers and workers
275 with regex substitutions in the name. Implement handling of such workers
276 in ap_proxy_get_worker(). Fixes the bug when regex workers were not
277 matched and used for request. PR 43513.
278 trunk patch: http://svn.apache.org/r1609680
279 http://svn.apache.org/r1609688
280 http://svn.apache.org/r1641381
281 ylavic: Merge patch provided (reusing new->real to avoid double de_socketfy() call).
282 Also added missing r1609688 to the patchset.
283 2.4.x patch: http://people.apache.org/~ylavic/httpd-2.4.x-ap_proxy_define_match_worker.patch
285 -0: covener tried to review this one in Austin with Jeff. Does the added match function
286 really cover a very narrow set of parameters with the way it skips over backreferences?
287 Also, why a new API vs. just setting the field inline?
289 * mod_systemd: New module, for integration with systemd on Linux.
290 trunk patch: http://svn.apache.org/r1393976
291 http://svn.apache.org/r1393997
292 http://svn.apache.org/r1484554
293 http://svn.apache.org/r1528032
294 http://svn.apache.org/r1528034
295 http://svn.apache.org/r1614821
296 http://svn.apache.org/r1618579
297 http://svn.apache.org/r1618588
298 2.4.x patch: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-mod_systemd.patch
300 sf comments: The IdleShutdown logic seems broken. Consider a single
301 active connection that is stalled for 10 seconds. That
302 connection will be broken after GracefulShutdownTimeout.
303 A better logic would be to check if there is any open
304 connection that is not in keep-alive state.
306 * mod_journald: Add new module mod_journald to log error logs into journald.
307 This patch needs changes done in mod_systemd patch (already
309 trunk patch: http://svn.apache.org/r1610339
310 http://svn.apache.org/r1621806
311 2.4.x patch: http://people.apache.org/~jkaluza/patches/httpd-2.4.x-mod_journald.patch
313 rjung, minfrin: Not understanding "This patch needs changes done in
314 mod_systemd patch", am I right in understanding this patch is
316 jkaluza: No, that patch is not committed yet. It is in STALLED section.
317 The link for that patch is: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-mod_systemd.patch
319 * core: Add support for systemd socket activation.
320 trunk patch: http://svn.apache.org/r1511033
321 http://svn.apache.org/r1608686
322 http://svn.apache.org/r1608694
323 http://svn.apache.org/r1608703
324 http://svn.apache.org/r1608721
325 http://svn.apache.org/r1608744
326 2.4.x patch: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-socket-activation.patch
329 * mod_proxy: Ensure network errors detected by the proxy are returned as
330 504 Gateway Timeout as opposed to 502 Bad Gateway
331 trunk patch: https://svn.apache.org/viewvc?view=revision&revision=1480058
332 2.4.x patch: trunk patch works modulo CHANGES
334 -1: rpluem: This change is still disputed. See
335 http://mail-archives.apache.org/mod_mbox/httpd-dev/201305.mbox/%3C1B16B9E3-87BA-4EEF-939C-7C7313B54714%40gbiv.com%3E
337 * cross-compile: allow to provide CC_FOR_BUILD so that gen_test_char will be
338 compiled by the build compiler instead of the host compiler.
339 Also set CC_FOR_BUILD to 'cc' when cross-compilation is detected.
340 Trunk patches: http://svn.apache.org/viewvc?view=revision&revision=1327907
341 http://svn.apache.org/viewvc?view=revision&revision=1328390
342 http://svn.apache.org/viewvc?view=revision&revision=1328714
343 2.4 patch: http://people.apache.org/~fuankg/diffs/httpd-2.4.x-cross_compile.diff
344 fuankg: on hold until we agree for a better and more simple solution ...
346 * Makefile.win: Added copying of .vbs / .wsf CGIs to Windows install target.
347 Moved fixing of shebang to separate target so that it is
348 no longer executed by default and all CGIs remain inactive.
349 trunk patch: http://svn.apache.org/viewvc?view=revision&revision=1387984
350 http://svn.apache.org/viewvc?view=revision&revision=1421203
351 http://svn.apache.org/viewvc?view=revision&revision=1421591
352 2.4.x patch: http://people.apache.org/~fuankg/diffs/httpd-2.4.x-Makefile.win.diff
355 This commit is essentially deciding that an httpd install on
356 Windows now has printenv/testcgi written in 2 more languages.
357 To the extent that the usefulness is that it shows how to make scripts
358 of these types executable by httpd, I believe that the documentation
359 is the proper place to solve that. To the extent that the usefullness
360 is to show how to implement a CGI in these particular languages, I believe
361 that the httpd distribution and documentation in general is not the
362 place for that. Historically these types of scripts have caused problems
363 for downstream vendorsas well as newbies (and sometimes the intersection
364 of those two groups) who don't understand that these are information leaks
365 once they are enabled, and the subtlety of the way they are disabled ("Apache
366 messed up the first line; let me fix that") contributes to that.
367 fuankg notes: I've just added a big warning to all CGI scripts which should now
368 make absolutely clear that these CGIs are for testing purpose only - so those
369 who enable those scripts with inserting the right shebang should be 100% aware
370 of any risks (this should cover your last point).
371 jim: trawick, does the above address your concerns?
372 trawick: to some extent (somebody reading the script gets an idea)
373 Why isn't the configuration requirement documented instead
374 of described indirectly in a sample?
375 Why are these new samples added to the install without three
376 votes? (I didn't veto it; put your name next to the two
377 existing ones and I'll be satisfied that enough people
378 considered this addition as an appropriate solution for a
379 real httpd usability problem.)
380 wrowe: I'd agree with trawick, and suggest that these scripts can begin
381 their life somewhere in the manual/ tree. This really seems like
382 the place where /usr/share/httpd/examples/ would be useful, but
383 there isn't an ordinary directory for that. Since we want none
384 of the scripts to function 'out of the box', what about a new
385 cgi-examples/ dir alongside cgi-bin/? Otherwise manual/cgi/examples
388 * core: block Define and Undefine in vhost and directory context. Because
389 it is EXEC_ON_READ, it "breaks out" of these contexts anyway.
390 trunk patch: http://svn.apache.org/r1656063
391 http://svn.apache.org/r1656122
392 2.4.x patch: http://people.apache.org/~covener/patches/2.4.x-define-limits.diff
393 +1: covener (I need to review the docs manually in this area)
394 -1: wrowe (blocking will break "working" .conf files on a subversion update
395 meant to pick up security fixes. "Alerting" I would agree to.)