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)
147 +1: ylavic, minfrin (with mmn bump for mpm_fdqueue.h)
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).
153 *) mpm_event: Do lingering close in worker(s).
154 trunk patch: http://svn.apache.org/r1823047
155 http://svn.apache.org/r1824454
156 http://svn.apache.org/r1824463
157 http://svn.apache.org/r1824464
158 http://svn.apache.org/r1824497
159 2.4.x patch: http://home.apache.org/~ylavic/patches/httpd-2.4.x-event-lingering_close_in_worker.patch
160 (trunk works if mpm_queue above is merged first, otherwise
161 the mpm_queue branch can also be synchronized after this
165 *) mod_ssl: Introduce SSLPolicy/SSLPolicyDefine directives.
166 trunk patch: http://svn.apache.org/r1805182
167 http://svn.apache.org/r1805186
168 http://svn.apache.org/r1808335
169 http://svn.apache.org/r1811475
170 http://svn.apache.org/r1817381
171 http://svn.apache.org/r1817894
172 2.4.x patch: https://svn.apache.org/repos/asf/httpd/httpd/patches/2.4.x/mod_ssl_policy.diff
174 minfrin: 2.4.x patch not applying for me, trunk patches work
175 icing: fixed the patch to include complete new files instead of svn's internal optimizations
178 PATCHES/ISSUES THAT ARE BEING WORKED
179 [ New entries should be added at the START of the list ]
181 *) mod_ssl: Return 502 instead of 500 when SSL peer check or
182 proxy_post_handshake hook fails.
183 Trunk patch: r1645529 (works)
184 2.4.x patch which adds CHANGES: https://emptyhammock.com/media/downloads/r1645529-to-2.4.x.txt
186 ylavic: there may be missing bits, see thread for commit r1736510.
188 *) core: Drop an invalid Last-Modified header value coming
189 from a (F)CGI script instead of replacing it with Unix epoch.
190 Warn the users about Last-Modified header value replacements
191 and violations of the RFC.
192 trunk patch: http://svn.apache.org/r1748379
193 http://svn.apache.org/r1750747
194 http://svn.apache.org/r1750749
195 http://svn.apache.org/r1750953
196 http://svn.apache.org/r1751138
197 http://svn.apache.org/r1751139
198 http://svn.apache.org/r1751147
199 http://svn.apache.org/r1757818
200 2.4.x: trunk patches work, final view:
201 http://home.apache.org/~elukey/httpd-2.4.x-core-last_modified_tz_logging.patch
202 The problem has been discussed in dev@ extensively but we did not reach a common
203 agreement about how to proceed in the long term. While we wait, I would really like
204 to introduce useful logs for the users (the starting point of this change was a users@
205 email thread). If this is not the right way to go I will move the patch to other
206 sections of STATUS (stalled or being worked).
207 The code has been tested with a simple PHP script returning different Last-Modified
208 headers (GMT now, GMT now Europe/Paris, GMT tomorrow, GMT yesterday, PST now).
211 *) http: Don't remove the Content-Length of zero from a HEAD response if
212 it comes from an origin server, module or script. Allow the previous
213 behaviour (for legacy/buggy modules only, not origin) by also backporting
214 the HttpContentLengthHeadZero directive (and also HttpExpectStrict which
215 comes for free with the same commit).
216 trunk patch: http://svn.apache.org/r1554303
217 http://svn.apache.org/r1678215
218 2.4.x patch: http://people.apache.org/~ylavic/httpd-2.4.x-preserve_head_cl_zero.patch
220 ylavic: r1554303 issued a major MMN bump, but since the ABI change is two
221 ints added at the end of core_server_config, the proposed merge
222 does a minor bump only.
223 minfrin: Two new directives need to be documented.
225 * mod_proxy_http: Don't establish or reuse a backend connection before pre-
226 fetching the request body, so to minimize the delay between it is supposed
227 to be alive and the first bytes sent: this is a best effort to prevent the
228 backend from closing because of idle or keepalive timeout in the meantime.
229 Also, handle a new "proxy-flushall" environment variable which allows to
230 flush any forwarded body data immediately. PR 56541+37920.
231 trunk patch: http://svn.apache.org/r1656259
232 http://svn.apache.org/r1656359 (CHANGES entry)
233 2.4.x patch: trunk works (modulo CHANGES, docs/log-message-tags)
235 -0: jim: This seems to be a hit to normal performance, to handle an
236 error and/or non-normal condition. The pre-fetch is
237 expensive, and is always done, even before we know that
238 the backend is available to rec' it. I understand the
239 error described, but is the fix actually worth it (plus
240 it seems to allow for a DDoS vector).
241 ylavic: It seems to me that the problem is real since we reuse the
242 connection before prefetching 16K (either controlled by the
243 client, or by an input filter), we currently always prefetch
244 these bytes already. Regarding performance I don't see any
245 difference (more cycles) compared with the current code.
246 However I think I failed to rebuild the header_brigade when
247 the proxy loop is retried (ping), so I need to rework this.
248 Do you think we'd better remove the prefetch, or maybe just
249 make it nonblocking (by default)?
250 jim: Non-blocking seems the best way to handle...
252 * mod_dav: Allow other modules to become providers and add ACLs
253 to the DAV response. Requires a release of apr-util v1.6.
254 trunk patch: http://svn.apache.org/r1748322
255 2.4.x: trunk works modulo CHANGES/MMN
257 rpluem asks: Will this compile with apr-util < v1.6 and keep
258 mod_dav working (without the new features of the patch of course)?
259 I doubt that we will require apr-util 1.6 for the lifetime of 2.4.x
260 (see the discussion around ap_cstr_casecmp[n] an apr 1.6)
261 minfrin: Yes, as you can see in the patch everything applies only
262 if APR_XML_X2T_PARSED is defined, and the patch was tested with
263 both apr-util v1.6 and apr-util v1.5.
264 -1: jorton, breaks binary backwards compat per dev@ discuss
265 msgid <20160902120654.GA12674@redhat.com>
266 (& also, making the structure change with apr-util version
267 means it breaks binary compat across an apr-util upgrade?)
269 * Support PCRE2 (10.x) in place of PCRE (8.x).
270 Submitted by: wrowe, Petr Pisar [ppisar redhat.com]
272 http://svn.apache.org/r1773454
273 http://svn.apache.org/r1773741
274 http://svn.apache.org/r1773742
275 http://svn.apache.org/r1773839
276 http://svn.apache.org/r1773870
277 http://svn.apache.org/r1773882
278 wrowe notes that the current code is too inefficient, owing to the fact
279 that the ovector is a required allocation and is no longer allocated on
280 the stack, by design. The correct fix is an apr userdata allocation on
281 the appropriate pool, which would be thread-safe, but the actual API of
282 ap_regexec[_len]() offers us no pool. We cannot associate that pool with
283 the ap_regex_t, because a single regex may be used by many threads in
284 parallel and is not thread-safe beyond initialization.
285 So the only fix allowing us to use PCRE 10 in httpd 2.4 would be to write
286 this as a thread safe storage buffer for the majority of cases (<10 $args)
287 and we don't have a portable tls mechanism to do so.
288 jorton: Adding ap_pregexec/_len which pass a pool would also work
289 for internal users of this api; not sure if performance
290 impact is significant from using malloc here.
293 PATCHES/ISSUES THAT ARE STALLED
295 * core: Add ap_errorlog_provider to make ErrorLog logging modular. This
296 backport keeps syslog logging as part of httpd core and only adds
297 API to allow other modules to be used for error logging.
298 trunk patch: http://svn.apache.org/r1525597
299 http://svn.apache.org/r1525664
300 http://svn.apache.org/r1525845
301 http://svn.apache.org/r1527003
302 http://svn.apache.org/r1527005
303 http://svn.apache.org/r1532344
304 http://svn.apache.org/r1539988
305 http://svn.apache.org/r1541029
306 http://svn.apache.org/r1543979
307 http://svn.apache.org/r1544156
308 http://svn.apache.org/r1626978
309 2.4.x patch: http://people.apache.org/~jkaluza/patches/httpd-2.4.x-errorlog_provider.patch
311 +1: covener w/ doc or code to fix syntax (providername:providerarg not supported like syslog or socacheproviders,
312 needs 2 args which is not valid in ErrorLog manual)
313 trawick: nit: fix "writing" in "/* NULL if we are writing to syslog */"
314 (sorry, haven't finished reviewing completely)
315 jim: What is the status of this??
317 * mod_proxy: Add ap_proxy_define_match_worker() and use it for ProxyPassMatch
318 and ProxyMatch section to distinguish between normal workers and workers
319 with regex substitutions in the name. Implement handling of such workers
320 in ap_proxy_get_worker(). Fixes the bug when regex workers were not
321 matched and used for request. PR 43513.
322 trunk patch: http://svn.apache.org/r1609680
323 http://svn.apache.org/r1609688
324 http://svn.apache.org/r1641381
325 ylavic: Merge patch provided (reusing new->real to avoid double de_socketfy() call).
326 Also added missing r1609688 to the patchset.
327 2.4.x patch: http://people.apache.org/~ylavic/httpd-2.4.x-ap_proxy_define_match_worker.patch
329 -0: covener tried to review this one in Austin with Jeff. Does the added match function
330 really cover a very narrow set of parameters with the way it skips over backreferences?
331 Also, why a new API vs. just setting the field inline?
333 * core: Add support for systemd socket activation.
334 trunk patch: http://svn.apache.org/r1511033
335 http://svn.apache.org/r1608686
336 http://svn.apache.org/r1608694
337 http://svn.apache.org/r1608703
338 http://svn.apache.org/r1608721
339 http://svn.apache.org/r1608744
340 2.4.x patch: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-socket-activation.patch
343 * mod_proxy: Ensure network errors detected by the proxy are returned as
344 504 Gateway Timeout as opposed to 502 Bad Gateway
345 trunk patch: https://svn.apache.org/viewvc?view=revision&revision=1480058
346 2.4.x patch: trunk patch works modulo CHANGES
348 -1: rpluem: This change is still disputed. See
349 http://mail-archives.apache.org/mod_mbox/httpd-dev/201305.mbox/%3C1B16B9E3-87BA-4EEF-939C-7C7313B54714%40gbiv.com%3E
351 * cross-compile: allow to provide CC_FOR_BUILD so that gen_test_char will be
352 compiled by the build compiler instead of the host compiler.
353 Also set CC_FOR_BUILD to 'cc' when cross-compilation is detected.
354 Trunk patches: http://svn.apache.org/viewvc?view=revision&revision=1327907
355 http://svn.apache.org/viewvc?view=revision&revision=1328390
356 http://svn.apache.org/viewvc?view=revision&revision=1328714
357 2.4 patch: http://people.apache.org/~fuankg/diffs/httpd-2.4.x-cross_compile.diff
358 fuankg: on hold until we agree for a better and more simple solution ...
360 * Makefile.win: Added copying of .vbs / .wsf CGIs to Windows install target.
361 Moved fixing of shebang to separate target so that it is
362 no longer executed by default and all CGIs remain inactive.
363 trunk patch: http://svn.apache.org/viewvc?view=revision&revision=1387984
364 http://svn.apache.org/viewvc?view=revision&revision=1421203
365 http://svn.apache.org/viewvc?view=revision&revision=1421591
366 2.4.x patch: http://people.apache.org/~fuankg/diffs/httpd-2.4.x-Makefile.win.diff
369 This commit is essentially deciding that an httpd install on
370 Windows now has printenv/testcgi written in 2 more languages.
371 To the extent that the usefulness is that it shows how to make scripts
372 of these types executable by httpd, I believe that the documentation
373 is the proper place to solve that. To the extent that the usefullness
374 is to show how to implement a CGI in these particular languages, I believe
375 that the httpd distribution and documentation in general is not the
376 place for that. Historically these types of scripts have caused problems
377 for downstream vendorsas well as newbies (and sometimes the intersection
378 of those two groups) who don't understand that these are information leaks
379 once they are enabled, and the subtlety of the way they are disabled ("Apache
380 messed up the first line; let me fix that") contributes to that.
381 fuankg notes: I've just added a big warning to all CGI scripts which should now
382 make absolutely clear that these CGIs are for testing purpose only - so those
383 who enable those scripts with inserting the right shebang should be 100% aware
384 of any risks (this should cover your last point).
385 jim: trawick, does the above address your concerns?
386 trawick: to some extent (somebody reading the script gets an idea)
387 Why isn't the configuration requirement documented instead
388 of described indirectly in a sample?
389 Why are these new samples added to the install without three
390 votes? (I didn't veto it; put your name next to the two
391 existing ones and I'll be satisfied that enough people
392 considered this addition as an appropriate solution for a
393 real httpd usability problem.)
394 wrowe: I'd agree with trawick, and suggest that these scripts can begin
395 their life somewhere in the manual/ tree. This really seems like
396 the place where /usr/share/httpd/examples/ would be useful, but
397 there isn't an ordinary directory for that. Since we want none
398 of the scripts to function 'out of the box', what about a new
399 cgi-examples/ dir alongside cgi-bin/? Otherwise manual/cgi/examples
402 *) mod_journald: Add new module mod_journald to log error logs into journald.
403 trunk patch: http://svn.apache.org/r1610339
404 http://svn.apache.org/r1621806
405 http://svn.apache.org/r1812339
406 2.4.x patch: http://people.apache.org/~jkaluza/patches/httpd-2.4.x-mod_journald.patch
407 http://svn.apache.org/r1812339
409 jchampion: Looks like the headers require GCC extensions to compile, so
410 mod_journald can't be configured in maintainer mode (-std=c89).
411 Can anyone else reproduce, or is it just my distro?
412 ylavic: missing r1812339 for maintainer-mode/c89/-Werror compliance,
413 needed if the above configure.in proposal gets backported.
414 Note that r1812339 could be backported in any case, even if
415 the above configure.in proposal does not get accepted.
417 * mod_systemd: New module, for integration with systemd on Linux.
418 trunk patch: http://svn.apache.org/r1393976
419 http://svn.apache.org/r1393997
420 http://svn.apache.org/r1484554
421 http://svn.apache.org/r1528032
422 http://svn.apache.org/r1528034
423 http://svn.apache.org/r1614821
424 http://svn.apache.org/r1618579
425 http://svn.apache.org/r1618588
426 2.4.x patch: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-mod_systemd.patch
428 sf comments: The IdleShutdown logic seems broken. Consider a single
429 active connection that is stalled for 10 seconds. That
430 connection will be broken after GracefulShutdownTimeout.
431 A better logic would be to check if there is any open
432 connection that is not in keep-alive state.