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 Documentation status is maintained separately and can be found at:
10 * docs/STATUS in this source tree, or
11 * http://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x/docs/STATUS
13 The current development branch of this software can be found at:
15 * http://svn.apache.org/repos/asf/httpd/httpd/trunk
17 Consult the following STATUS files for information on related projects:
19 * http://svn.apache.org/repos/asf/apr/apr/trunk/STATUS
20 * http://svn.apache.org/repos/asf/apr/apr/branches/1.4.x/STATUS
21 * http://svn.apache.org/repos/asf/apr/apr-util/branches/1.4.x/STATUS
22 * http://svn.apache.org/repos/asf/apr/apr/branches/1.5.x/STATUS
23 * http://svn.apache.org/repos/asf/apr/apr-util/branches/1.5.x/STATUS
25 Patches considered for backport are noted in their branches' STATUS:
27 * http://svn.apache.org/repos/asf/httpd/httpd/branches/2.0.x/STATUS
28 * http://svn.apache.org/repos/asf/httpd/httpd/branches/2.2.x/STATUS
29 * http://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x/STATUS
34 [NOTE that x.{odd}.z versions are strictly Alpha/Beta releases,
35 while x.{even}.z versions are Stable/GA releases.]
37 2.4.13 : In development.
38 2.4.12 : Tagged on January 22, 2015. Released Jan 29, 2015
39 2.4.11 : Tagged on January 15, 2015. Not released.
40 2.4.10 : Tagged on July 15, 2014. Released July 21, 2014
41 2.4.9 : Tagged on March 13, 2014. Released on March 17, 2014
42 2.4.8 : Tagged on March 11, 2014. Not released.
43 2.4.7 : Tagged on November 19, 2013. Released on Nov 25, 2013
44 2.4.6 : Tagged on July 15, 2013. Released July, 22, 2013
45 2.4.5 : Tagged on July 11, 2013, not released.
46 2.4.4 : Tagged on February 18, 2013. Released Feb 25, 2013
47 2.4.3 : Tagged on August 17, 2012. Released Aug 18, 2012
48 2.4.2 : Tagged on April 5, 2012. Released Apr 17, 2012.
49 2.4.1 : Tagged on February 13, 2012. Released Feb 21, 2012.
50 2.4.0 : Tagged on January 16, 2012, not released.
51 2.3.16 : Tagged on December 15, 2011.
52 2.3.15 : Tagged on November 8, 2011. Released Nov. 15, 2011.
53 2.3.14 : Tagged on August 1, 2011. Released Aug. 9, 2011.
54 2.3.13 : Tagged on June 28, 2011, not released.
55 2.3.12 : Tagged on May 11, 2011. Released May 23, 2011.
56 2.3.11 : Released as Beta on March 7, 2011.
57 2.3.10 : Tagged on December 13, 2010. Released Dec 21, 2010.
58 2.3.9 : Tagged on November 23, 2010, not released.
59 2.3.8 : Tagged on August 24, 2010.
60 2.3.7 : Tagged on August 19, 2010, not released.
61 2.3.6 : Released on June 21, 2010.
62 2.3.5 : Released on January 26, 2010.
63 2.3.4 : Released on December 8, 2009.
64 2.3.3 : Tagged on November 11, 2009, not released.
65 2.3.2 : Tagged on March 23, 2009, not released.
66 2.3.1 : Tagged on January 2, 2009, not released.
67 2.3.0 : Tagged on December 6, 2008, not released.
69 Contributors looking for a mission:
71 * Just do an egrep on "TODO" or "XXX" in the source.
73 * Review the bug database at: http://issues.apache.org/bugzilla/
75 * Review the "PatchAvailable" bugs in the bug database:
77 https://issues.apache.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Apache+httpd-2&keywords=PatchAvailable
79 After testing, you can append a comment saying "Reviewed and tested".
81 * Open bugs in the bug database.
83 * See also the STATUS file in the docs/ directory, which lists documentation-specific TODO items.
86 CURRENT RELEASE NOTES:
88 * Forward binary compatibility is expected of Apache 2.4.x releases, such
89 that no MMN major number changes will occur after 2.4.1. Such changes can
90 only be made in the trunk.
92 * All commits to branches/2.4.x must be reflected in SVN trunk,
93 as well, if they apply. Logical progression is commit to trunk
94 then merge into branches/2.4.x, as applicable.
96 * Current exceptions for RTC for this branch:
100 . non-Unix, single-platform code
102 RELEASE SHOWSTOPPERS:
105 PATCHES ACCEPTED TO BACKPORT FROM TRUNK:
106 [ start all new proposals below, under PATCHES PROPOSED. ]
110 PATCHES PROPOSED TO BACKPORT FROM TRUNK:
111 [ New proposals should be added at the end of the list ]
113 * mod_proxy: Add ap_proxy_define_match_worker() and use it for ProxyPassMatch
114 and ProxyMatch section to distinguish between normal workers and workers
115 with regex substitutions in the name. Implement handling of such workers
116 in ap_proxy_get_worker(). Fixes the bug when regex workers were not
117 matched and used for request. PR 43513.
118 trunk patch: http://svn.apache.org/r1609680
119 http://svn.apache.org/r1609688
120 http://svn.apache.org/r1641381
121 ylavic: Merge patch provided (reusing new->real to avoid double de_socketfy() call).
122 Also added missing r1609688 to the patchset.
123 2.4.x patch: http://people.apache.org/~ylavic/httpd-2.4.x-ap_proxy_define_match_worker.patch
125 -0: covener tried to review this one in Austin with Jeff. Does the added match function
126 really cover a very narrow set of parameters with the way it skips over backreferences?
127 Also, why a new API vs. just setting the field inline?
129 * core: Add ap_errorlog_provider to make ErrorLog logging modular. This
130 backport keeps syslog logging as part of httpd core and only adds
131 API to allow other modules to be used for error logging.
132 trunk patch: http://svn.apache.org/r1525597
133 http://svn.apache.org/r1525664
134 http://svn.apache.org/r1525845
135 http://svn.apache.org/r1527003
136 http://svn.apache.org/r1527005
137 http://svn.apache.org/r1532344
138 http://svn.apache.org/r1539988
139 http://svn.apache.org/r1541029
140 http://svn.apache.org/r1543979
141 http://svn.apache.org/r1544156
142 http://svn.apache.org/r1626978
143 2.4.x patch: http://people.apache.org/~jkaluza/patches/httpd-2.4.x-errorlog_provider.patch
145 +1: covener w/ doc or code to fix syntax (providername:providerarg not supported like syslog or socacheproviders,
146 needs 2 args which is not valid in ErrorLog manual)
147 trawick: nit: fix "writing" in "/* NULL if we are writting to syslog */"
148 (sorry, haven't finished reviewing completely)
150 * mod_journald: Add new module mod_journald to log error logs into journald.
151 This patch needs changes done in mod_systemd patch (already
153 trunk patch: http://svn.apache.org/r1610339
154 http://svn.apache.org/r1621806
155 2.4.x patch: http://people.apache.org/~jkaluza/patches/httpd-2.4.x-mod_journald.patch
157 wrowe: approves as experimental, 'with-modules=all' restriction
158 satisfies the concern I'd otherwise have.
160 * MPMs: Support SO_REUSEPORT to create multiple duplicated listener
161 records for scalability (full log in 2.4.x patch).
162 trunk patch: http://svn.apache.org/r1599531
163 http://svn.apache.org/r1599593
164 http://svn.apache.org/r1599601
165 http://svn.apache.org/r1599603
166 http://svn.apache.org/r1601558
167 http://svn.apache.org/r1629909
168 http://svn.apache.org/r1629918
169 http://svn.apache.org/r1629990
170 http://svn.apache.org/r1635521
171 http://svn.apache.org/r1635859
172 http://svn.apache.org/r1640145
173 http://svn.apache.org/r1640161
174 http://svn.apache.org/r1640184
175 http://svn.apache.org/r1640763
176 http://svn.apache.org/r1643179
177 http://svn.apache.org/r1656368
178 http://svn.apache.org/r1679714
179 2.4.x patch: http://people.apache.org/~ylavic/httpd-2.4.x-ap_listeners_buckets-v3.patch
182 *) http: Don't remove the Content-Length of zero from a HEAD response if
183 it comes from an origin server, module or script. Allow the previous
184 behaviour (for legacy/buggy modules only, not origin) by also backporting
185 the HttpContentLengthHeadZero directive (and also HttpExpectStrict which
186 comes for free with the same commit).
187 trunk patch: http://svn.apache.org/r1554303
188 http://svn.apache.org/r1678215
189 2.4.x patch: http://people.apache.org/~ylavic/httpd-2.4.x-preserve_head_cl_zero.patch
191 ylavic: r1554303 issued a major MMN bump, but since the ABI change is two
192 ints added at the end of core_server_config, the proposed merge
193 does a minor bump only.
195 *) mod_ssl: add ALPN support by allowing other modules to register callbacks
196 for negotiation of the application layer protocol. PR 52210.
197 trunk patch: http://svn.apache.org/r1332643
198 http://svn.apache.org/r1487772
199 http://svn.apache.org/r1670397
200 http://svn.apache.org/r1670434
201 http://svn.apache.org/r1670436
202 http://svn.apache.org/r1670578
203 http://svn.apache.org/r1670738
204 http://svn.apache.org/r1675459
205 http://svn.apache.org/r1676004
206 http://svn.apache.org/r1676709
207 http://svn.apache.org/r1681741
208 http://svn.apache.org/r1681746
209 2.4.x patch: http://people.apache.org/~ylavic/httpd-2.4.x-alpn-v4.patch
211 ylavic: we'd better comment on @dev for this one for Stefan Eissing (who
212 proposed the merge) to be able to follow (and comment too).
214 *) mod_proxy: Don't put the worker in error state for 500 or 503 errors
215 returned by the backend unless failonstatus is configured to. PR 56925.
216 trunk patch: http://svn.apache.org/r1681694
217 trunk patch: http://svn.apache.org/r1682907
218 2.4.x patch: trunk works (modulo CHANGES)
222 PATCHES/ISSUES THAT ARE BEING WORKED
224 * mod_proxy_http: Don't establish or reuse a backend connection before pre-
225 fetching the request body, so to minimize the delay between it is supposed
226 to be alive and the first bytes sent: this is a best effort to prevent the
227 backend from closing because of idle or keepalive timeout in the meantime.
228 Also, handle a new "proxy-flushall" environment variable which allows to
229 flush any forwarded body data immediately. PR 56541+37920.
230 trunk patch: http://svn.apache.org/r1656259
231 http://svn.apache.org/r1656359 (CHANGES entry)
232 2.4.x patch: trunk works (modulo CHANGES, docs/log-message-tags)
234 -0: jim: This seems to be a hit to normal performance, to handle an
235 error and/or non-normal condition. The pre-fetch is
236 expensive, and is always done, even before we know that
237 the backend is available to rec' it. I understand the
238 error described, but is the fix actually worth it (plus
239 it seems to allow for a DDoS vector).
240 ylavic: It seems to me that the problem is real since we reuse the
241 connection before prefetching 16K (either controlled by the
242 client, or by an input filter), we currently always prefetch
243 these bytes already. Regarding performance I don't see any
244 difference (more cycles) compared with the current code.
245 However I think I failed to rebuild the header_brigade when
246 the proxy loop is retried (ping), so I need to rework this.
247 Do you think we'd better remove the prefetch, or maybe just
248 make it nonblocking (by default)?
249 jim: Non-blocking seems the best way to handle...
252 PATCHES/ISSUES THAT ARE STALLED
254 * mod_systemd: New module, for integration with systemd on Linux.
255 trunk patch: http://svn.apache.org/r1393976
256 http://svn.apache.org/r1393997
257 http://svn.apache.org/r1484554
258 http://svn.apache.org/r1528032
259 http://svn.apache.org/r1528034
260 http://svn.apache.org/r1614821
261 http://svn.apache.org/r1618579
262 http://svn.apache.org/r1618588
263 2.4.x patch: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-mod_systemd.patch
266 * core: Add support for systemd socket activation.
267 trunk patch: http://svn.apache.org/r1511033
268 http://svn.apache.org/r1608686
269 http://svn.apache.org/r1608694
270 http://svn.apache.org/r1608703
271 http://svn.apache.org/r1608721
272 http://svn.apache.org/r1608744
273 2.4.x patch: http://people.apache.org/~jkaluza/patches/mod_systemd/httpd-2.4.x-socket-activation.patch
276 * mod_proxy: Ensure network errors detected by the proxy are returned as
277 504 Gateway Timout as opposed to 502 Bad Gateway
278 trunk patch: https://svn.apache.org/viewvc?view=revision&revision=1480058
279 2.4.x patch: trunk patch works modulo CHANGES
281 -1: rpluem: This change is still disputed. See
282 http://mail-archives.apache.org/mod_mbox/httpd-dev/201305.mbox/%3C1B16B9E3-87BA-4EEF-939C-7C7313B54714%40gbiv.com%3E
284 * cross-compile: allow to provide CC_FOR_BUILD so that gen_test_char will be
285 compiled by the build compiler instead of the host compiler.
286 Also set CC_FOR_BUILD to 'cc' when cross-compilation is detected.
287 Trunk patches: http://svn.apache.org/viewvc?view=revision&revision=1327907
288 http://svn.apache.org/viewvc?view=revision&revision=1328390
289 http://svn.apache.org/viewvc?view=revision&revision=1328714
290 2.4 patch: http://people.apache.org/~fuankg/diffs/httpd-2.4.x-cross_compile.diff
291 fuankg: on hold until we agree for a better and more simple solution ...
293 * Makefile.win: Added copying of .vbs / .wsf CGIs to Windows install target.
294 Moved fixing of shebang to separate target so that it is
295 no longer executed by default and all CGIs remain inactive.
296 trunk patch: http://svn.apache.org/viewvc?view=revision&revision=1387984
297 http://svn.apache.org/viewvc?view=revision&revision=1421203
298 http://svn.apache.org/viewvc?view=revision&revision=1421591
299 2.4.x patch: http://people.apache.org/~fuankg/diffs/httpd-2.4.x-Makefile.win.diff
302 This commit is essentially deciding that an httpd install on
303 Windows now has printenv/testcgi written in 2 more languages.
304 To the extent that the usefulness is that it shows how to make scripts
305 of these types executable by httpd, I believe that the documentation
306 is the proper place to solve that. To the extent that the usefullness
307 is to show how to implement a CGI in these particular languages, I believe
308 that the httpd distribution and documentation in general is not the
309 place for that. Historically these types of scripts have caused problems
310 for downstream vendorsas well as newbies (and sometimes the intersection
311 of those two groups) who don't understand that these are information leaks
312 once they are enabled, and the subtlety of the way they are disabled ("Apache
313 messed up the first line; let me fix that") contributes to that.
314 fuankg notes: I've just added a big warning to all CGI scripts which should now
315 make absolutely clear that these CGIs are for testing purpose only - so those
316 who enable those scripts with inserting the right shebang should be 100% aware
317 of any risks (this should cover your last point).
318 jim: trawick, does the above address your concerns?
319 trawick: to some extent (somebody reading the script gets an idea)
320 Why isn't the configuration requirement documented instead
321 of described indirectly in a sample?
322 Why are these new samples added to the install without three
323 votes? (I didn't veto it; put your name next to the two
324 existing ones and I'll be satisified that enough people
325 considered this addition as an appropriate solution for a
326 real httpd usability problem.)
327 wrowe: I'd agree with trawick, and suggest that these scripts can begin
328 their life somewhere in the manual/ tree. This really seems like
329 the place where /usr/share/httpd/examples/ would be useful, but
330 there isn't an ordinary directory for that. Since we want none
331 of the scripts to function 'out of the box', what about a new
332 cgi-examples/ dir alongside cgi-bin/? Otherwise manual/cgi/examples