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.31 : In development.
33 2.4.30 : Tagged on February 19, 2018, not released.
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_dav: Allow other modules to become providers and add ACLs
128 trunk patch: http://svn.apache.org/r1748322
129 http://svn.apache.org/r1824590
130 http://svn.apache.org/r1824596
131 2.4.x: trunk works modulo CHANGES/MMN/log-message
133 -1: rpluem: While we allow extensions of structures at the end in general
134 this is a specific case where the the design of the mod_dav
135 API clashes with this approach, as the API requires consumers
136 to create the public structs on their own, something we do
137 not "allow/encourage" otherwise in order to be able to do the
138 structure extension. I don't want to see consumers of this API
139 suffer from the clash we created.
141 https://lists.apache.org/thread.html/b924afe0fcc58a8636b753e630421bf6dc2080653a79575fd5fd641a@%3Cdev.httpd.apache.org%3E
143 *) mod_proxy_fcgi: Add the support for the mod_proxy's flushpackets parameter.
144 trunk patch: http://svn.apache.org/r1802040
145 http://svn.apache.org/r1807876
146 http://svn.apache.org/r1808014
147 http://svn.apache.org/r1805490
148 http://svn.apache.org/r1823886
149 2.4.x: svn merge -c 1802040,1807876,1808014,1805490,1823886 ^/httpd/httpd/trunk .
151 elukey: this patch has been requested a couple of times in the users@ mailing list,
152 but from my tests in trunk the async/set-aside core features would already
153 do the job without the need of this patch. I am proposing the backport
154 to allow more users to migrate away from mod_fastcgi.
156 *) Use liblua paths from pkg-config if available [jorton]
157 Fixes unexpected addition of -L/usr/lib for mod_lua
158 trunk patch: http://svn.apache.org/r1825147
161 *) Permit package root paths to --with-libxml2= configure option
162 trunk patch: http://svn.apache.org/r1825169
166 PATCHES/ISSUES THAT ARE BEING WORKED
167 [ New entries should be added at the START of the list ]
169 *) mod_ssl: Return 502 instead of 500 when SSL peer check or
170 proxy_post_handshake hook fails.
171 Trunk patch: r1645529 (works)
172 2.4.x patch which adds CHANGES: https://emptyhammock.com/media/downloads/r1645529-to-2.4.x.txt
174 ylavic: there may be missing bits, see thread for commit r1736510.
176 *) core: Drop an invalid Last-Modified header value coming
177 from a (F)CGI script instead of replacing it with Unix epoch.
178 Warn the users about Last-Modified header value replacements
179 and violations of the RFC.
180 trunk patch: http://svn.apache.org/r1748379
181 http://svn.apache.org/r1750747
182 http://svn.apache.org/r1750749
183 http://svn.apache.org/r1750953
184 http://svn.apache.org/r1751138
185 http://svn.apache.org/r1751139
186 http://svn.apache.org/r1751147
187 http://svn.apache.org/r1757818
188 2.4.x: trunk patches work, final view:
189 http://home.apache.org/~elukey/httpd-2.4.x-core-last_modified_tz_logging.patch
190 The problem has been discussed in dev@ extensively but we did not reach a common
191 agreement about how to proceed in the long term. While we wait, I would really like
192 to introduce useful logs for the users (the starting point of this change was a users@
193 email thread). If this is not the right way to go I will move the patch to other
194 sections of STATUS (stalled or being worked).
195 The code has been tested with a simple PHP script returning different Last-Modified
196 headers (GMT now, GMT now Europe/Paris, GMT tomorrow, GMT yesterday, PST now).
199 *) http: Don't remove the Content-Length of zero from a HEAD response if
200 it comes from an origin server, module or script. Allow the previous
201 behaviour (for legacy/buggy modules only, not origin) by also backporting
202 the HttpContentLengthHeadZero directive (and also HttpExpectStrict which
203 comes for free with the same commit).
204 trunk patch: http://svn.apache.org/r1554303
205 http://svn.apache.org/r1678215
206 2.4.x patch: http://people.apache.org/~ylavic/httpd-2.4.x-preserve_head_cl_zero.patch
208 ylavic: r1554303 issued a major MMN bump, but since the ABI change is two
209 ints added at the end of core_server_config, the proposed merge
210 does a minor bump only.
211 minfrin: Two new directives need to be documented.
213 * mod_proxy_http: Don't establish or reuse a backend connection before pre-
214 fetching the request body, so to minimize the delay between it is supposed
215 to be alive and the first bytes sent: this is a best effort to prevent the
216 backend from closing because of idle or keepalive timeout in the meantime.
217 Also, handle a new "proxy-flushall" environment variable which allows to
218 flush any forwarded body data immediately. PR 56541+37920.
219 trunk patch: http://svn.apache.org/r1656259
220 http://svn.apache.org/r1656359 (CHANGES entry)
221 2.4.x patch: trunk works (modulo CHANGES, docs/log-message-tags)
223 -0: jim: This seems to be a hit to normal performance, to handle an
224 error and/or non-normal condition. The pre-fetch is
225 expensive, and is always done, even before we know that
226 the backend is available to rec' it. I understand the
227 error described, but is the fix actually worth it (plus
228 it seems to allow for a DDoS vector).
229 ylavic: It seems to me that the problem is real since we reuse the
230 connection before prefetching 16K (either controlled by the
231 client, or by an input filter), we currently always prefetch
232 these bytes already. Regarding performance I don't see any
233 difference (more cycles) compared with the current code.
234 However I think I failed to rebuild the header_brigade when
235 the proxy loop is retried (ping), so I need to rework this.
236 Do you think we'd better remove the prefetch, or maybe just
237 make it nonblocking (by default)?
238 jim: Non-blocking seems the best way to handle...
240 * Support PCRE2 (10.x) in place of PCRE (8.x).
241 Submitted by: wrowe, Petr Pisar [ppisar redhat.com]
243 http://svn.apache.org/r1773454
244 http://svn.apache.org/r1773741
245 http://svn.apache.org/r1773742
246 http://svn.apache.org/r1773839
247 http://svn.apache.org/r1773870
248 http://svn.apache.org/r1773882
249 wrowe notes that the current code is too inefficient, owing to the fact
250 that the ovector is a required allocation and is no longer allocated on
251 the stack, by design. The correct fix is an apr userdata allocation on
252 the appropriate pool, which would be thread-safe, but the actual API of
253 ap_regexec[_len]() offers us no pool. We cannot associate that pool with
254 the ap_regex_t, because a single regex may be used by many threads in
255 parallel and is not thread-safe beyond initialization.
256 So the only fix allowing us to use PCRE 10 in httpd 2.4 would be to write
257 this as a thread safe storage buffer for the majority of cases (<10 $args)
258 and we don't have a portable tls mechanism to do so.
259 jorton: Adding ap_pregexec/_len which pass a pool would also work
260 for internal users of this api; not sure if performance
261 impact is significant from using malloc here.
264 PATCHES/ISSUES THAT ARE STALLED
266 * core: Add ap_errorlog_provider to make ErrorLog logging modular. This
267 backport keeps syslog logging as part of httpd core and only adds
268 API to allow other modules to be used for error logging.
269 trunk patch: http://svn.apache.org/r1525597
270 http://svn.apache.org/r1525664
271 http://svn.apache.org/r1525845
272 http://svn.apache.org/r1527003
273 http://svn.apache.org/r1527005
274 http://svn.apache.org/r1532344
275 http://svn.apache.org/r1539988
276 http://svn.apache.org/r1541029
277 http://svn.apache.org/r1543979
278 http://svn.apache.org/r1544156
279 http://svn.apache.org/r1626978
280 2.4.x patch: http://people.apache.org/~jkaluza/patches/httpd-2.4.x-errorlog_provider.patch
282 +1: covener w/ doc or code to fix syntax (providername:providerarg not supported like syslog or socacheproviders,
283 needs 2 args which is not valid in ErrorLog manual)
284 trawick: nit: fix "writing" in "/* NULL if we are writing to syslog */"
285 (sorry, haven't finished reviewing completely)
286 jim: What is the status of this??
288 * mod_proxy: Add ap_proxy_define_match_worker() and use it for ProxyPassMatch
289 and ProxyMatch section to distinguish between normal workers and workers
290 with regex substitutions in the name. Implement handling of such workers
291 in ap_proxy_get_worker(). Fixes the bug when regex workers were not
292 matched and used for request. PR 43513.
293 trunk patch: http://svn.apache.org/r1609680
294 http://svn.apache.org/r1609688
295 http://svn.apache.org/r1641381
296 ylavic: Merge patch provided (reusing new->real to avoid double de_socketfy() call).
297 Also added missing r1609688 to the patchset.
298 2.4.x patch: http://people.apache.org/~ylavic/httpd-2.4.x-ap_proxy_define_match_worker.patch
300 -0: covener tried to review this one in Austin with Jeff. Does the added match function
301 really cover a very narrow set of parameters with the way it skips over backreferences?
302 Also, why a new API vs. just setting the field inline?
304 * core: Add support for systemd socket activation.
305 trunk patch: http://svn.apache.org/r1511033
306 http://svn.apache.org/r1608686
307 http://svn.apache.org/r1608694
308 http://svn.apache.org/r1608703
309 http://svn.apache.org/r1608721
310 http://svn.apache.org/r1608744
311 2.4.x patch: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-socket-activation.patch
314 * mod_proxy: Ensure network errors detected by the proxy are returned as
315 504 Gateway Timeout as opposed to 502 Bad Gateway
316 trunk patch: https://svn.apache.org/viewvc?view=revision&revision=1480058
317 2.4.x patch: trunk patch works modulo CHANGES
319 -1: rpluem: This change is still disputed. See
320 http://mail-archives.apache.org/mod_mbox/httpd-dev/201305.mbox/%3C1B16B9E3-87BA-4EEF-939C-7C7313B54714%40gbiv.com%3E
322 * cross-compile: allow to provide CC_FOR_BUILD so that gen_test_char will be
323 compiled by the build compiler instead of the host compiler.
324 Also set CC_FOR_BUILD to 'cc' when cross-compilation is detected.
325 Trunk patches: http://svn.apache.org/viewvc?view=revision&revision=1327907
326 http://svn.apache.org/viewvc?view=revision&revision=1328390
327 http://svn.apache.org/viewvc?view=revision&revision=1328714
328 2.4 patch: http://people.apache.org/~fuankg/diffs/httpd-2.4.x-cross_compile.diff
329 fuankg: on hold until we agree for a better and more simple solution ...
331 * Makefile.win: Added copying of .vbs / .wsf CGIs to Windows install target.
332 Moved fixing of shebang to separate target so that it is
333 no longer executed by default and all CGIs remain inactive.
334 trunk patch: http://svn.apache.org/viewvc?view=revision&revision=1387984
335 http://svn.apache.org/viewvc?view=revision&revision=1421203
336 http://svn.apache.org/viewvc?view=revision&revision=1421591
337 2.4.x patch: http://people.apache.org/~fuankg/diffs/httpd-2.4.x-Makefile.win.diff
340 This commit is essentially deciding that an httpd install on
341 Windows now has printenv/testcgi written in 2 more languages.
342 To the extent that the usefulness is that it shows how to make scripts
343 of these types executable by httpd, I believe that the documentation
344 is the proper place to solve that. To the extent that the usefullness
345 is to show how to implement a CGI in these particular languages, I believe
346 that the httpd distribution and documentation in general is not the
347 place for that. Historically these types of scripts have caused problems
348 for downstream vendorsas well as newbies (and sometimes the intersection
349 of those two groups) who don't understand that these are information leaks
350 once they are enabled, and the subtlety of the way they are disabled ("Apache
351 messed up the first line; let me fix that") contributes to that.
352 fuankg notes: I've just added a big warning to all CGI scripts which should now
353 make absolutely clear that these CGIs are for testing purpose only - so those
354 who enable those scripts with inserting the right shebang should be 100% aware
355 of any risks (this should cover your last point).
356 jim: trawick, does the above address your concerns?
357 trawick: to some extent (somebody reading the script gets an idea)
358 Why isn't the configuration requirement documented instead
359 of described indirectly in a sample?
360 Why are these new samples added to the install without three
361 votes? (I didn't veto it; put your name next to the two
362 existing ones and I'll be satisfied that enough people
363 considered this addition as an appropriate solution for a
364 real httpd usability problem.)
365 wrowe: I'd agree with trawick, and suggest that these scripts can begin
366 their life somewhere in the manual/ tree. This really seems like
367 the place where /usr/share/httpd/examples/ would be useful, but
368 there isn't an ordinary directory for that. Since we want none
369 of the scripts to function 'out of the box', what about a new
370 cgi-examples/ dir alongside cgi-bin/? Otherwise manual/cgi/examples
373 *) mod_journald: Add new module mod_journald to log error logs into journald.
374 trunk patch: http://svn.apache.org/r1610339
375 http://svn.apache.org/r1621806
376 http://svn.apache.org/r1812339
377 2.4.x patch: http://people.apache.org/~jkaluza/patches/httpd-2.4.x-mod_journald.patch
378 http://svn.apache.org/r1812339
380 jchampion: Looks like the headers require GCC extensions to compile, so
381 mod_journald can't be configured in maintainer mode (-std=c89).
382 Can anyone else reproduce, or is it just my distro?
383 ylavic: missing r1812339 for maintainer-mode/c89/-Werror compliance,
384 needed if the above configure.in proposal gets backported.
385 Note that r1812339 could be backported in any case, even if
386 the above configure.in proposal does not get accepted.
388 * mod_systemd: New module, for integration with systemd on Linux.
389 trunk patch: http://svn.apache.org/r1393976
390 http://svn.apache.org/r1393997
391 http://svn.apache.org/r1484554
392 http://svn.apache.org/r1528032
393 http://svn.apache.org/r1528034
394 http://svn.apache.org/r1614821
395 http://svn.apache.org/r1618579
396 http://svn.apache.org/r1618588
397 2.4.x patch: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-mod_systemd.patch
399 sf comments: The IdleShutdown logic seems broken. Consider a single
400 active connection that is stalled for 10 seconds. That
401 connection will be broken after GracefulShutdownTimeout.
402 A better logic would be to check if there is any open
403 connection that is not in keep-alive state.