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