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 The current development branch of this software can be found at:
10 * http://svn.apache.org/repos/asf/httpd/httpd/trunk
12 Consult the following STATUS files for information on related projects:
14 * http://svn.apache.org/repos/asf/apr/apr/trunk/STATUS
15 * http://svn.apache.org/repos/asf/apr/apr/branches/1.4.x/STATUS
16 * http://svn.apache.org/repos/asf/apr/apr-util/branches/1.4.x/STATUS
17 * http://svn.apache.org/repos/asf/apr/apr/branches/1.5.x/STATUS
18 * http://svn.apache.org/repos/asf/apr/apr-util/branches/1.5.x/STATUS
19 * http://svn.apache.org/repos/asf/apr/apr/branches/1.6.x/STATUS
20 * http://svn.apache.org/repos/asf/apr/apr-util/branches/1.6.x/STATUS
22 Patches considered for backport are noted in their branches' STATUS:
24 * http://svn.apache.org/repos/asf/httpd/httpd/branches/2.2.x/STATUS
25 * http://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x/STATUS
29 [NOTE that x.{odd}.z versions are strictly Alpha/Beta releases,
30 while x.{even}.z versions are Stable/GA releases.]
32 2.4.30 : In development. Jim proposes a T&R sometime between Jan 24
34 2.4.29 : Tagged on October 17, 2017. Released on October 23, 2017.
35 2.4.28 : Tagged on September 25, 2017. Released on October 5, 2017.
36 2.4.27 : Tagged on July 6, 2017. Released on July 11, 2017.
37 2.4.26 : Tagged on June 13, 2017. Released on June 19, 2017.
38 2.4.25 : Tagged on December 16, 2016. Released on December 21, 2016.
39 2.4.24 : Tagged on December 16, 2016, not released.
40 2.4.23 : Tagged on June 30, 2016. Released on July 05, 2016.
41 2.4.22 : Tagged on June 20, 2016, not released.
42 2.4.21 : Tagged on June 16, 2016, not released.
43 2.4.20 : Tagged on April 4, 2016. Released on April 11, 2016.
44 2.4.19 : Tagged on March 21, 2016, not released.
45 2.4.18 : Tagged on December 8, 2015. Released on December 14, 2015.
46 2.4.17 : Tagged on October 9, 2015. Released October 13, 2015.
47 2.4.16 : Tagged on July 9, 2015. Released July 15, 2015
48 2.4.15 : Tagged on June 19, 2015. Not released.
49 2.4.14 : Tagged on June 11, 2015. Not released.
50 2.4.13 : Tagged on June 4, 2015. Not released.
51 2.4.12 : Tagged on January 22, 2015. Released Jan 29, 2015
52 2.4.11 : Tagged on January 15, 2015. Not released.
53 2.4.10 : Tagged on July 15, 2014. Released July 21, 2014
54 2.4.9 : Tagged on March 13, 2014. Released on March 17, 2014
55 2.4.8 : Tagged on March 11, 2014. Not released.
56 2.4.7 : Tagged on November 19, 2013. Released on Nov 25, 2013
57 2.4.6 : Tagged on July 15, 2013. Released July, 22, 2013
58 2.4.5 : Tagged on July 11, 2013, not released.
59 2.4.4 : Tagged on February 18, 2013. Released Feb 25, 2013
60 2.4.3 : Tagged on August 17, 2012. Released Aug 18, 2012
61 2.4.2 : Tagged on April 5, 2012. Released Apr 17, 2012.
62 2.4.1 : Tagged on February 13, 2012. Released Feb 21, 2012.
63 2.4.0 : Tagged on January 16, 2012, not released.
64 2.3.16 : Tagged on December 15, 2011.
65 2.3.15 : Tagged on November 8, 2011. Released Nov. 15, 2011.
66 2.3.14 : Tagged on August 1, 2011. Released Aug. 9, 2011.
67 2.3.13 : Tagged on June 28, 2011, not released.
68 2.3.12 : Tagged on May 11, 2011. Released May 23, 2011.
69 2.3.11 : Released as Beta on March 7, 2011.
70 2.3.10 : Tagged on December 13, 2010. Released Dec 21, 2010.
71 2.3.9 : Tagged on November 23, 2010, not released.
72 2.3.8 : Tagged on August 24, 2010.
73 2.3.7 : Tagged on August 19, 2010, not released.
74 2.3.6 : Released on June 21, 2010.
75 2.3.5 : Released on January 26, 2010.
76 2.3.4 : Released on December 8, 2009.
77 2.3.3 : Tagged on November 11, 2009, not released.
78 2.3.2 : Tagged on March 23, 2009, not released.
79 2.3.1 : Tagged on January 2, 2009, not released.
80 2.3.0 : Tagged on December 6, 2008, not released.
82 Contributors looking for a mission:
84 * Just do an egrep on "TODO" or "XXX" in the source.
86 * Review the bug database at: http://issues.apache.org/bugzilla/
88 * Review the "PatchAvailable" bugs in the bug database:
90 https://issues.apache.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Apache+httpd-2&keywords=PatchAvailable
92 After testing, you can append a comment saying "Reviewed and tested".
94 * Open bugs in the bug database.
96 * See also the STATUS file in the docs/ directory, which lists documentation-specific TODO items.
99 CURRENT RELEASE NOTES:
101 * Forward binary compatibility is expected of Apache 2.4.x releases, such
102 that no MMN major number changes will occur after 2.4.1. Such changes can
103 only be made in the trunk.
105 * All commits to branches/2.4.x must be reflected in SVN trunk,
106 as well, if they apply. Logical progression is commit to trunk
107 then merge into branches/2.4.x, as applicable.
109 * Current exceptions for RTC for this branch:
114 . non-Unix, single-platform code
116 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_remoteip: Add PROXY protocol support
127 trunk patch: http://svn.apache.org/r1776575
128 http://svn.apache.org/r1776578 (doc fix)
129 http://svn.apache.org/r1776627 (shortened name + doc fix)
130 http://svn.apache.org/r1776674 (attribution moved to CHANGES)
131 http://svn.apache.org/r1776740 (attribution updated in mod_remotip.c)
132 http://svn.apache.org/r1778268 (fix compiler warning)
133 http://svn.apache.org/r1780725 (set buckets aside)
134 http://svn.apache.org/r1781030 (fix strict GCC warning)
135 http://svn.apache.org/r1781031 (reference the filter by handle)
136 http://svn.apache.org/r1781701 (rework optional processing case)
137 http://svn.apache.org/r1788674 (final edge cases/ignore slave conns)
138 http://svn.apache.org/r1789800 (remove optional processing)
139 http://svn.apache.org/r1790169 (rename "exception" directive)
140 http://svn.apache.org/r1790457 (Update directive name in err message)
141 http://svn.apache.org/r1806985
142 http://svn.apache.org/r1818279
143 2.4 convenience patch (includes CHANGES):
144 http://home.apache.org/~jim/patches/RemoteIPProxyProtocol.2.4-v2.patch
145 http://svn.apache.org/r1818279
147 ylavic: RemoteIPProxyProtocol* are documented as scoped to server config
148 and virtual host, though using ap_server_conf makes them global
149 only (thus less useful too...).
150 jim: Can docco patch be post-backport?
151 minfrin: The docs seem correct, and there is a long explanation in the docs of
152 why the scoping is as it is.
153 +1 with this to fix a warning:
154 http://svn.apache.org/r1776734
156 *) proxy_util: Schemes and hostnames that are "too long" are
157 no longer automatically fatal errors but are instead logged
158 and truncated, at which point the admin can determine if that
160 trunk patch: http://svn.apache.org/r1823482
161 2.4.x patch: trunk works
164 *) logresolve: Fix segfault with logresolve -c and IPv6
165 Due to a logic error, there could be a NULL pointer dereference.
167 trunk patch: http://svn.apache.org/r1745863
168 http://svn.apache.org/r1745864
169 2.4.x patch: trunk works
170 +1: jailletc36, minfrin
172 *) mod_proxy: Provide an RFC1035 compliant version of the hostname in the
173 proxy_worker_shared structure. PR62085
174 trunk patch: http://svn.apache.org/r1824176
175 2.4.x patch: trunk works
179 PATCHES/ISSUES THAT ARE BEING WORKED
180 [ New entries should be added at the START of the list ]
182 *) mod_ssl: Return 502 instead of 500 when SSL peer check or
183 proxy_post_handshake hook fails.
184 Trunk patch: r1645529 (works)
185 2.4.x patch which adds CHANGES: https://emptyhammock.com/media/downloads/r1645529-to-2.4.x.txt
187 ylavic: there may be missing bits, see thread for commit r1736510.
189 *) core: Drop an invalid Last-Modified header value coming
190 from a (F)CGI script instead of replacing it with Unix epoch.
191 Warn the users about Last-Modified header value replacements
192 and violations of the RFC.
193 trunk patch: http://svn.apache.org/r1748379
194 http://svn.apache.org/r1750747
195 http://svn.apache.org/r1750749
196 http://svn.apache.org/r1750953
197 http://svn.apache.org/r1751138
198 http://svn.apache.org/r1751139
199 http://svn.apache.org/r1751147
200 http://svn.apache.org/r1757818
201 2.4.x: trunk patches work, final view:
202 http://home.apache.org/~elukey/httpd-2.4.x-core-last_modified_tz_logging.patch
203 The problem has been discussed in dev@ extensively but we did not reach a common
204 agreement about how to proceed in the long term. While we wait, I would really like
205 to introduce useful logs for the users (the starting point of this change was a users@
206 email thread). If this is not the right way to go I will move the patch to other
207 sections of STATUS (stalled or being worked).
208 The code has been tested with a simple PHP script returning different Last-Modified
209 headers (GMT now, GMT now Europe/Paris, GMT tomorrow, GMT yesterday, PST now).
212 *) http: Don't remove the Content-Length of zero from a HEAD response if
213 it comes from an origin server, module or script. Allow the previous
214 behaviour (for legacy/buggy modules only, not origin) by also backporting
215 the HttpContentLengthHeadZero directive (and also HttpExpectStrict which
216 comes for free with the same commit).
217 trunk patch: http://svn.apache.org/r1554303
218 http://svn.apache.org/r1678215
219 2.4.x patch: http://people.apache.org/~ylavic/httpd-2.4.x-preserve_head_cl_zero.patch
221 ylavic: r1554303 issued a major MMN bump, but since the ABI change is two
222 ints added at the end of core_server_config, the proposed merge
223 does a minor bump only.
224 minfrin: Two new directives need to be documented.
226 * mod_proxy_http: Don't establish or reuse a backend connection before pre-
227 fetching the request body, so to minimize the delay between it is supposed
228 to be alive and the first bytes sent: this is a best effort to prevent the
229 backend from closing because of idle or keepalive timeout in the meantime.
230 Also, handle a new "proxy-flushall" environment variable which allows to
231 flush any forwarded body data immediately. PR 56541+37920.
232 trunk patch: http://svn.apache.org/r1656259
233 http://svn.apache.org/r1656359 (CHANGES entry)
234 2.4.x patch: trunk works (modulo CHANGES, docs/log-message-tags)
236 -0: jim: This seems to be a hit to normal performance, to handle an
237 error and/or non-normal condition. The pre-fetch is
238 expensive, and is always done, even before we know that
239 the backend is available to rec' it. I understand the
240 error described, but is the fix actually worth it (plus
241 it seems to allow for a DDoS vector).
242 ylavic: It seems to me that the problem is real since we reuse the
243 connection before prefetching 16K (either controlled by the
244 client, or by an input filter), we currently always prefetch
245 these bytes already. Regarding performance I don't see any
246 difference (more cycles) compared with the current code.
247 However I think I failed to rebuild the header_brigade when
248 the proxy loop is retried (ping), so I need to rework this.
249 Do you think we'd better remove the prefetch, or maybe just
250 make it nonblocking (by default)?
251 jim: Non-blocking seems the best way to handle...
253 * mod_dav: Allow other modules to become providers and add ACLs
254 to the DAV response. Requires a release of apr-util v1.6.
255 trunk patch: http://svn.apache.org/r1748322
256 2.4.x: trunk works modulo CHANGES/MMN
258 rpluem asks: Will this compile with apr-util < v1.6 and keep
259 mod_dav working (without the new features of the patch of course)?
260 I doubt that we will require apr-util 1.6 for the lifetime of 2.4.x
261 (see the discussion around ap_cstr_casecmp[n] an apr 1.6)
262 minfrin: Yes, as you can see in the patch everything applies only
263 if APR_XML_X2T_PARSED is defined, and the patch was tested with
264 both apr-util v1.6 and apr-util v1.5.
265 -1: jorton, breaks binary backwards compat per dev@ discuss
266 msgid <20160902120654.GA12674@redhat.com>
267 (& also, making the structure change with apr-util version
268 means it breaks binary compat across an apr-util upgrade?)
270 * Support PCRE2 (10.x) in place of PCRE (8.x).
271 Submitted by: wrowe, Petr Pisar [ppisar redhat.com]
273 http://svn.apache.org/r1773454
274 http://svn.apache.org/r1773741
275 http://svn.apache.org/r1773742
276 http://svn.apache.org/r1773839
277 http://svn.apache.org/r1773870
278 http://svn.apache.org/r1773882
279 wrowe notes that the current code is too inefficient, owing to the fact
280 that the ovector is a required allocation and is no longer allocated on
281 the stack, by design. The correct fix is an apr userdata allocation on
282 the appropriate pool, which would be thread-safe, but the actual API of
283 ap_regexec[_len]() offers us no pool. We cannot associate that pool with
284 the ap_regex_t, because a single regex may be used by many threads in
285 parallel and is not thread-safe beyond initialization.
286 So the only fix allowing us to use PCRE 10 in httpd 2.4 would be to write
287 this as a thread safe storage buffer for the majority of cases (<10 $args)
288 and we don't have a portable tls mechanism to do so.
289 jorton: Adding ap_pregexec/_len which pass a pool would also work
290 for internal users of this api; not sure if performance
291 impact is significant from using malloc here.
294 PATCHES/ISSUES THAT ARE STALLED
296 * core: Add ap_errorlog_provider to make ErrorLog logging modular. This
297 backport keeps syslog logging as part of httpd core and only adds
298 API to allow other modules to be used for error logging.
299 trunk patch: http://svn.apache.org/r1525597
300 http://svn.apache.org/r1525664
301 http://svn.apache.org/r1525845
302 http://svn.apache.org/r1527003
303 http://svn.apache.org/r1527005
304 http://svn.apache.org/r1532344
305 http://svn.apache.org/r1539988
306 http://svn.apache.org/r1541029
307 http://svn.apache.org/r1543979
308 http://svn.apache.org/r1544156
309 http://svn.apache.org/r1626978
310 2.4.x patch: http://people.apache.org/~jkaluza/patches/httpd-2.4.x-errorlog_provider.patch
312 +1: covener w/ doc or code to fix syntax (providername:providerarg not supported like syslog or socacheproviders,
313 needs 2 args which is not valid in ErrorLog manual)
314 trawick: nit: fix "writing" in "/* NULL if we are writing to syslog */"
315 (sorry, haven't finished reviewing completely)
316 jim: What is the status of this??
318 * mod_proxy: Add ap_proxy_define_match_worker() and use it for ProxyPassMatch
319 and ProxyMatch section to distinguish between normal workers and workers
320 with regex substitutions in the name. Implement handling of such workers
321 in ap_proxy_get_worker(). Fixes the bug when regex workers were not
322 matched and used for request. PR 43513.
323 trunk patch: http://svn.apache.org/r1609680
324 http://svn.apache.org/r1609688
325 http://svn.apache.org/r1641381
326 ylavic: Merge patch provided (reusing new->real to avoid double de_socketfy() call).
327 Also added missing r1609688 to the patchset.
328 2.4.x patch: http://people.apache.org/~ylavic/httpd-2.4.x-ap_proxy_define_match_worker.patch
330 -0: covener tried to review this one in Austin with Jeff. Does the added match function
331 really cover a very narrow set of parameters with the way it skips over backreferences?
332 Also, why a new API vs. just setting the field inline?
334 * core: Add support for systemd socket activation.
335 trunk patch: http://svn.apache.org/r1511033
336 http://svn.apache.org/r1608686
337 http://svn.apache.org/r1608694
338 http://svn.apache.org/r1608703
339 http://svn.apache.org/r1608721
340 http://svn.apache.org/r1608744
341 2.4.x patch: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-socket-activation.patch
344 * mod_proxy: Ensure network errors detected by the proxy are returned as
345 504 Gateway Timeout as opposed to 502 Bad Gateway
346 trunk patch: https://svn.apache.org/viewvc?view=revision&revision=1480058
347 2.4.x patch: trunk patch works modulo CHANGES
349 -1: rpluem: This change is still disputed. See
350 http://mail-archives.apache.org/mod_mbox/httpd-dev/201305.mbox/%3C1B16B9E3-87BA-4EEF-939C-7C7313B54714%40gbiv.com%3E
352 * cross-compile: allow to provide CC_FOR_BUILD so that gen_test_char will be
353 compiled by the build compiler instead of the host compiler.
354 Also set CC_FOR_BUILD to 'cc' when cross-compilation is detected.
355 Trunk patches: http://svn.apache.org/viewvc?view=revision&revision=1327907
356 http://svn.apache.org/viewvc?view=revision&revision=1328390
357 http://svn.apache.org/viewvc?view=revision&revision=1328714
358 2.4 patch: http://people.apache.org/~fuankg/diffs/httpd-2.4.x-cross_compile.diff
359 fuankg: on hold until we agree for a better and more simple solution ...
361 * Makefile.win: Added copying of .vbs / .wsf CGIs to Windows install target.
362 Moved fixing of shebang to separate target so that it is
363 no longer executed by default and all CGIs remain inactive.
364 trunk patch: http://svn.apache.org/viewvc?view=revision&revision=1387984
365 http://svn.apache.org/viewvc?view=revision&revision=1421203
366 http://svn.apache.org/viewvc?view=revision&revision=1421591
367 2.4.x patch: http://people.apache.org/~fuankg/diffs/httpd-2.4.x-Makefile.win.diff
370 This commit is essentially deciding that an httpd install on
371 Windows now has printenv/testcgi written in 2 more languages.
372 To the extent that the usefulness is that it shows how to make scripts
373 of these types executable by httpd, I believe that the documentation
374 is the proper place to solve that. To the extent that the usefullness
375 is to show how to implement a CGI in these particular languages, I believe
376 that the httpd distribution and documentation in general is not the
377 place for that. Historically these types of scripts have caused problems
378 for downstream vendorsas well as newbies (and sometimes the intersection
379 of those two groups) who don't understand that these are information leaks
380 once they are enabled, and the subtlety of the way they are disabled ("Apache
381 messed up the first line; let me fix that") contributes to that.
382 fuankg notes: I've just added a big warning to all CGI scripts which should now
383 make absolutely clear that these CGIs are for testing purpose only - so those
384 who enable those scripts with inserting the right shebang should be 100% aware
385 of any risks (this should cover your last point).
386 jim: trawick, does the above address your concerns?
387 trawick: to some extent (somebody reading the script gets an idea)
388 Why isn't the configuration requirement documented instead
389 of described indirectly in a sample?
390 Why are these new samples added to the install without three
391 votes? (I didn't veto it; put your name next to the two
392 existing ones and I'll be satisfied that enough people
393 considered this addition as an appropriate solution for a
394 real httpd usability problem.)
395 wrowe: I'd agree with trawick, and suggest that these scripts can begin
396 their life somewhere in the manual/ tree. This really seems like
397 the place where /usr/share/httpd/examples/ would be useful, but
398 there isn't an ordinary directory for that. Since we want none
399 of the scripts to function 'out of the box', what about a new
400 cgi-examples/ dir alongside cgi-bin/? Otherwise manual/cgi/examples
403 *) mod_journald: Add new module mod_journald to log error logs into journald.
404 trunk patch: http://svn.apache.org/r1610339
405 http://svn.apache.org/r1621806
406 http://svn.apache.org/r1812339
407 2.4.x patch: http://people.apache.org/~jkaluza/patches/httpd-2.4.x-mod_journald.patch
408 http://svn.apache.org/r1812339
410 jchampion: Looks like the headers require GCC extensions to compile, so
411 mod_journald can't be configured in maintainer mode (-std=c89).
412 Can anyone else reproduce, or is it just my distro?
413 ylavic: missing r1812339 for maintainer-mode/c89/-Werror compliance,
414 needed if the above configure.in proposal gets backported.
415 Note that r1812339 could be backported in any case, even if
416 the above configure.in proposal does not get accepted.
418 * mod_systemd: New module, for integration with systemd on Linux.
419 trunk patch: http://svn.apache.org/r1393976
420 http://svn.apache.org/r1393997
421 http://svn.apache.org/r1484554
422 http://svn.apache.org/r1528032
423 http://svn.apache.org/r1528034
424 http://svn.apache.org/r1614821
425 http://svn.apache.org/r1618579
426 http://svn.apache.org/r1618588
427 2.4.x patch: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-mod_systemd.patch
429 sf comments: The IdleShutdown logic seems broken. Consider a single
430 active connection that is stalled for 10 seconds. That
431 connection will be broken after GracefulShutdownTimeout.
432 A better logic would be to check if there is any open
433 connection that is not in keep-alive state.