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