1 APACHE 2.3 STATUS: -*-text-*-
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/trunk/STATUS
8 Documentation status is maintained seperately and can be found at:
10 * docs/STATUS in this source tree, or
11 * http://svn.apache.org/repos/asf/httpd/httpd/trunk/docs/STATUS
13 Consult the following STATUS files for information on related projects:
15 * http://svn.apache.org/repos/asf/apr/apr/trunk/STATUS
16 * http://svn.apache.org/repos/asf/apr/apr-util/trunk/STATUS
18 Patches considered for backport are noted in their branches' STATUS:
20 * http://svn.apache.org/repos/asf/httpd/httpd/branches/2.0.x/STATUS
21 * http://svn.apache.org/repos/asf/httpd/httpd/branches/2.2.x/STATUS
26 [NOTE that x.{odd}.z versions are strictly Alpha/Beta releases,
27 while x.{even}.z versions are Stable/GA releases.]
29 2.3.16 : In Development.
30 2.3.15 : Tagged on November 8, 2011.
31 2.3.14 : Tagged on August 1, 2011. Released Aug. 9, 2011.
32 2.3.13 : Tagged on June 28, 2011, not released.
33 2.3.12 : Tagged on May 11, 2011. Released May 23, 2011.
34 2.3.11 : Released as Beta on March 7, 2011.
35 2.3.10 : Tagged on December 13, 2010. Released Dec 21, 2010.
36 2.3.9 : Tagged on November 23, 2010, not released.
37 2.3.8 : Tagged on August 24, 2010.
38 2.3.7 : Tagged on August 19, 2010, not released.
39 2.3.6 : Released on June 21, 2010.
40 2.3.5 : Released on January 26, 2010.
41 2.3.4 : Released on December 8, 2009.
42 2.3.3 : Tagged on November 11, 2009, not released.
43 2.3.2 : Tagged on March 23, 2009, not released.
44 2.3.1 : Tagged on January 2, 2009, not released.
45 2.3.0 : Tagged on December 6, 2008, not released.
47 Contributors looking for a mission:
49 * Just do an egrep on "TODO" or "XXX" in the source.
51 * Review the bug database at: http://issues.apache.org/bugzilla/
53 * Review the "PatchAvailable" bugs in the bug database:
55 https://issues.apache.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Apache+httpd-2&keywords=PatchAvailable
57 After testing, you can append a comment saying "Reviewed and tested".
59 * Open bugs in the bug database.
61 * See also the STATUS file in the docs/ directory, which lists documentation-specific TODO items.
64 CURRENT RELEASE NOTES:
69 Jim proposes final beta release the mid/end of Sept, with a
70 GA in October (at the latest). Jim volunteers to RM these.
76 * Modules that are not ready for production use must be removed.
77 The same for modules without documentation.
79 These modulese will be removed after branching 2.4.x from trunk.
80 If anyone disagrees, please comment.
82 - MPM simple (unfinished; buggy)
83 - mod_serf (which is optimal for async httpd anyways; didn't work
84 with MPM event last time sf tested it)
85 - mod_noloris (in experimental; obsoleted by mod_reqtimeout)
87 See https://svn.apache.org/repos/asf/httpd/httpd/trunk/docs/STATUS
88 under 'modules docs' for a more comprehensive list of undocumented modules.
90 * The mod_session* modules need to be checked that their hooks respect
91 the returning of int (HTTP status codes) and apr_status_t as appropriate,
92 and any anomolies fixed.
93 jim sez: from what I can see, mod_session* is no worse that other
94 modules that mix these 2 types... clean up is
95 forthcoming but should not be considered a blocker, imo
97 wrowe asks: what's the API change required?
98 wrowe asks; why are we shipping this if it requires apr_ssl
100 * mod_ssl's proxy support only allows one proxy client certificate per
101 frontend virtual host. Lift this restriction.
102 jim sez: Why a blocker?, pgollucci +1 jim
103 wrowe asks: what's the API change required?
105 * INCLUDE mod_fcgid with 2.4.0, esp to help php users etc to enjoy
106 a painless event mpm experience.
107 sf: can be done in 2.4.x>0
109 * Decide and document the API guarantees for mod_lua. Current consensous at
110 the hackathon seems to be that mod_lua should be released as experimental
111 with a note that the API may change during 2.4.x.
113 * mpm_event can abort under very high load with
114 (17)File exists: process_socket: apr_pollset_add failure
115 file event.c, line 952, assertion "rc == 0" failed
116 child pid 18196 exit signal Aborted (6)
121 OLD ISSUES THAT WERE THOUGHT TO BE SHOWSTOPPERS FOR 2.2 BUT OBVIOUSLY WEREN'T:
123 * Handling of non-trailing / config by non-default handler is broken
124 http://marc.theaimsgroup.com/?l=apache-httpd-dev&m=105451701628081&w=2
125 jerenkrantz asks: Why should this block a release?
126 wsanchez agrees: this may be a change in behavior, but isn't
127 clearly wrong, and even if so, it doesn't seem like a
130 * the edge connection filter cannot be removed
131 http://marc.theaimsgroup.com/?l=apache-httpd-dev&m=105366252619530&w=2
133 jerenkrantz asks: Why should this block a release?
135 stas replies: because it requires a rewrite of the filters stack
136 implementation (you have suggested that) and once 2.2 is
137 released you can't do that anymore.
139 pgollucci: this affects mod_perl I'm pretty sure.
143 * Name the Server (version 2.4 or 3.0, depending on the final call)
144 Recent discussion indicates we should designate a (short name).
145 This is not yet a [Vote] - Your nominations please:
146 * Apache HTTP Server (httpd)
147 +1: sctemme (why mess with it?), pgollucci
149 RELEASE NON-SHOWSTOPPERS BUT WOULD BE REAL NICE TO WRAP THESE UP:
151 * Clean up all the kruft and *extremely* outdated stuff below...
153 * Maybe remove Limit/LimitExcept or at least make it log warnings when
156 * Patches submitted to the bug database:
157 http://issues.apache.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Apache+httpd-2&keywords=PatchAvailable
159 * Filter stacks and subrequests, redirects and fast redirects.
160 There's at least one PR that suffers from the current unclean behaviour
161 (which lets the server send garbage): PR 17629
162 nd says: Every subrequest should get its own filter stack with the
163 subreq_core filter as bottom-most. That filter does two things:
164 - swallow EOS buckets
165 - redirect the data stream to the upper request's (rr->main)
166 filter chain directly after the subrequest's starting
168 Once we have a clean solution, we can try to optimize
169 it, so that the server won't be slow down too much.
171 * RFC 2616 violations.
172 Closed PRs: 15852, 15857, 15859, 15861, 15864, 15869, 15870, 16120,
173 16125, 16135, 16136, 16137, 16138, 16139, 16140, 16518,
175 Open PRs: 15865, 15866, 15868, 16126, 16133, 16142, 16521, 42978
176 jerenkrantz says: need to decide how many we need to backport and/or
177 if these rise to showstopper status.
178 wrowe suggests: it would be nice to see "MUST" v.s. "SHOULD" v.s. "MAY"
179 out of this list, without reviewing them individually.
181 * pipes deadlock on all platforms with limited pipe buffers (e.g. both
182 Linux and Win32, as opposed to only Win32 on 1.3). The right solution
183 is either GStein's proposal for a "CGI Brigade", or OtherBill's proposal
184 for "Poll Buckets" for "Polling Filter Chains". Or maybe both :-)
186 * All handlers should always send content down even if r->header_only
187 is set. If not, it means that the HEAD requests don't generate the
188 same headers as a GET which is wrong.
190 * exec cmd and suexec arg-passing enhancements
191 Status: Patches proposed
192 Message-ID: <20020526041748.A29148@prodigy.Redbrick.DCU.IE>
193 (see the "proc.patch" and "suexec-shell.patch" links in this message)
195 * The 2.0.36 worker MPM graceless shutdown changes work but are
196 a bit clunky on some platforms; eg, on Linux, the loop to
197 join each worker thread seems to hang, and the parent ends up
198 killing off the child with SIGKILL. But at least it shuts down.
200 chrisd: Has this been fixed by the changes for PR 38737?
202 * We do not properly substitute the prefix-variables in the configuration
203 scripts or generated-configs. (i.e. if sysconfdir is etc,
204 httpd-std.conf points to conf.)
206 * If any request gets through ap_process_request_internal() and is
207 scheduled to be served by the core handler, without a flag that this
208 r->filename was tested by dir/file_walk, we need to 500 at the very
209 end of the ap_process_request_internal() processing so sub_req-esters
210 know this request cannot be run. This provides authors of older
211 modules better compatibility, while still improving the security and
214 Status: still need to decide where this goes, OtherBill comments...
215 Message-ID: <065701c14526$495203b0$96c0b0d0@roweclan.net>
216 [Deleted comments regarding the ap_run_handler phase, as irrelevant
217 as BillS points out that "common case will be caught in
218 default_handler already (with the r->finfo.filetype == 0 check)"
219 and the issue is detecting this -before- we try to run the req.]
221 gregames says: can this happen somehow without a broken module
222 being involved? If not, why waste cycles trying to defend against
223 potential broken modules? It seems futile.
224 wrowe counters: no, it shouldn't happen unless the module is broken.
225 But the right answer is to fail the request up-front in dir/file
226 walk if the path was entirely invalid; and we can't do that either
227 UNTIL 2.1 or we break modules that haven't hooked map_to_storage.
229 * Can a static httpd be built reliably?
230 Message-ID: <20020207142751.T31582@clove.org>
232 * Usage of APR_BRIGADE_NORMALIZE in core_input_filter should be
235 <Pine.LNX.4.33.0201202232430.318-100000@deepthought.cs.virginia.edu>
236 Jeff wonders if we still care about this. It is no longer an
237 API issue but simply an extra trip through the brigade.
239 * Try to get libtool inter-library dependency code working on AIX.
240 Message-ID: <cm3n10lx555.fsf@rdu163-40-092.nc.rr.com>
242 Justin says: If we get it working on AIX, we can enable this
243 on all platforms and clean up our build system somewhat.
244 Jeff says: I thought I tested a patch for you sometime in
245 January that you were going to commit within a few days.
247 * Handling of %2f in URIs. Currently both 1.3 and 2.0
248 completely disallow %2f in the request URI path (see
249 ap_unescape_url() in util.c). It's permitted and passed
250 through in the query string, however. Roy says the
251 original reason for disallowing it, from five years ago,
252 was to protect CGI scripts that applied PATH_INFO to
253 a filesystem location and which might be tricked by
254 ..%2f..%2f(...). We *should* allow path-info of the
255 form 'http://foo.com/index.cgi/path/to/path%2finfo'.
256 Since we've revamped a lot of our processing of path
257 segments, it would be nice to allow this, or at least
258 allow it conditionally with a directive.
260 OtherBill adds that %2f as the SECOND character of a multibyte
261 sequence causes the request to fail! This happens notably in
264 * There is increasing demand from module writers for an API
265 that will allow them to control the server à la apachectl.
266 Reasons include sole-function servers that need to die if
267 an external dependency (e.g., a database) fails, et cetera.
268 Perhaps something in the (ever more abused) scoreboard?
270 On the other hand, we already have a pipe that goes between parent
271 and child for graceful shutdown events, along with an API that
272 can be used to send a message down that pipe. In threaded MPMs,
273 it is easy enough to make that one pipe be used for graceful
274 and graceless events, and it is also easy to open that pipe
275 to both parent and child for writing. Then we just need to
276 figure out how to do graceless on non-threaded MPMs.
278 * Allow the DocumentRoot directive within <Location > scopes? This
279 allows the beloved (crusty) Alias /foo/ /somepath/foo/ followed
280 by a <Directory /somepath/foo> to become simply
281 <Location /foo/> DocumentRoot /somefile/foo (IMHO a bit more legible
282 and in-your-face.) DocumentRoot unset would be accepted [and would
283 not permit content to be served, only virtual resources such as
284 server-info or server-status.
285 This proposed change would _not_ depricate Alias.
286 striker: See the thread starting with Message-ID:
287 JLEGKKNELMHCJPNMOKHOGEEJFBAA.striker@apache.org.
289 * Win32: Rotatelogs sometimes is not terminated when Apache
290 goes down hard. FirstBill was looking at possibly tracking the
291 child's-child processes in the parent process.
292 stoddard: Shared scoreboard might offer a good way for the parent
293 to keep track of 'other child' processes and whack them if the child
295 Other thoughts on walking the process chain using the NT kernel
296 have also been proposed on APR.
298 * Eliminate unnecessary creation of pipes in mod_cgid
300 * Combine log_child and piped_log_spawn. Clean up http_log.c.
303 * Platforms that do not support fork (primarily Win32 and AS/400)
304 Architect start-up code that avoids initializing all the modules
305 in the parent process on platforms that do not support fork.
307 * There are still a number of places in the code where we are
308 losing error status (i.e. throwing away the error returned by a
309 system call and replacing it with a generic error code)
311 * Mass vhosting version of suEXEC.
313 * All DBMs suffer from confusion in support/dbmmanage (perl script) since
314 the dbmmanage employs the first-matched dbm format. This is not
315 necessarily the library that Apache was built with. Aught to
316 rewrite dbmmanage upon installation to bin/ with the proper library
317 for predictable mod_auth_dbm administration.
318 Questions; htdbm exists, time to kill dbmmanage, or does it remain
319 useful as a perl dbm management example? If we keep it,
320 do we address the issue above?
323 Some additional items remaining:
324 - case_preserved_filename stuff
325 (use the new canonical name stuff?)
326 - find a new home for ap_text(_header)
327 - is it possible to remove the DAV: namespace stuff from util_xml?
329 * ap_core_translate() and its use by mod_mmap_static and mod_file_cache
330 are a bit wonky. The function should probably be exposed as a utility
331 function (such as ap_translate_url2fs() or ap_validate_fs_url() or
332 something). Another approach would be a new hook phase after
333 "translate" which would allow the module to munge what the
334 translation has decided to do.
335 Status: Greg +1 (volunteers)
337 * Explore use of a post-config hook for the code in http_main.c which
338 calls ap_fixup_virutal_hosts(), ap_fini_vhost_config(), and
339 ap_sort_hooks() [to reduce the logic in main()]
341 * read the config tree just once, and process N times (as necessary)
343 * (possibly) use UUIDs in mod_unique_id and/or mod_usertrack
345 * (possibly) port the bug fix for PR 6942 (segv when LoadModule is put
346 into a VirtualHost container) to 2.0.
348 * shift stuff to mod_core.h
350 * callers of ap_run_create_request() should check the return value
351 for failure (Doug volunteers)
353 * Fix the worker MPM to use POD to kill child processes instead
354 of ap_os_killpg, regardless of how they should die.
356 chrisd: Is this done, by any chance? See r92598 and r93358.
358 * Scoreboard structures could be changed in the future such that
359 proper alignment is not maintained, leading to segfaults on
360 some systems. Cliff posted a patch to deal with this issue but
361 later recanted. See this message to dev@apr.apache.org:
363 <Pine.LNX.4.44.0203011354090.16457-200000@deepthought.cs.virginia.edu>
365 * APXS either needs to be fixed completely for use when apr is out of tree,
366 or it should drop query mode altogether, and we just grow an
367 httpd-config or similar arrangement.
368 To quote a discussion in STATUS earlier:
370 thommay: this doesn't fix all the problems with apxs and out of
371 tree apr/apr-util, but it's a good start. There's still the
372 query cases; but I'm beginning to think that in these cases
373 the app should be querying ap{r,u}-config directly
374 deprecate -q: add htpd-config: gstein, pquerna, minfrin, pgollucci
377 TODO ISSUES REMAINING IN MOD_SSL:
379 * Do we need SSL_set_read_ahead()?
381 * SSLRequire directive (parsing of) leaks memory
383 * Diffie-Hellman-Parameters for temporary keys are hardcoded in
384 ssl_engine_dh.c, while the comment in ssl_engine_kernel.c says:
385 "it is suggested that keys be changed daily or every 500
386 transactions, and more often if possible."
388 * ssl_var_lookup could be rewritten to be MUCH faster
390 * CRL callback should be pluggable
392 * session cache store should be pluggable
394 * init functions should return status code rather than ssl_die()
396 * ssl_engine_pphrase.c needs to be reworked so it is generic enough
397 to also decrypt proxy keys
399 * output warning when allowing SSL v2.0 ? its so old
402 * mod_proxy: Ability to run SSL over proxy gateway connections,
403 encrypting (or reencrypting) at the proxy.
405 * mod_cache: Handle ESI tags.
407 * mod_cache: Resolve issue of how to cache page fragments (or perhaps
408 -if- we want to cache page fragments). Today, mod_cache/mod_mem_cache
409 will cache #include 'virtual' requests (but not #include 'file'
410 requests). This was accomplished by making CACHE_IN a
411 CONTENT_SET-1 filter to force it to run before the SUBREQ_CORE
412 filter. But now responses cannot be cached that include the
413 effects of having been run through CONTENT_SET filters
414 (mod_deflate, mod_expires, etc). We could rerun all the
415 CONTENT_SET filters on the cached response, but this will not
416 work in all cases. For example, mod_expires relies on installing
417 the EXPIRATION filter during fixups. Contents served out of
418 mod_cache (out of the quick_handler) bypass -all- the request
419 line server hooks (Ryan really hated this. It is great for
420 performance, but bad because of the complications listed above).
422 mod_cache/mod_mem_cache/mod_cache_disk:
424 * mod_mem_cache: Consider adding a RevalidateTimeout directive to
425 specify time at which local cached content is to be revalidated
426 (ie, underlying file stat'ed to see if it has changed).
428 * mod_cache: CacheEnable/CacheDisable should accept regular expressions.
429 jerenkrantz says: Too slow. Get regexs away from speedy caches by
430 default. Introduce a new CacheEnableRegex if you want.
432 * mod_mem_cache/mod_cache_disk: Need to be able to query cache
433 status (num of entries, cache object properties, etc.).
434 mod_status could be extended to query optional hooks defined
435 by modules for the purpose of reporting module status.
436 mod_cache (et. al.) could define optional hooks that are called
437 to collect status. Status should be queryable by
439 jerenkrantz says: Yawn. Who cares.
441 * Regex containers don't work in an intutive way
442 Status: No one has come up with an efficient way to fix this
443 behavior. Dean has suggested getting rid of regex containers
445 OtherBill suggests: We at least seem to agree on eliminating
446 the <Container ~ foo> forms, and using only
447 <ContainerMatch foo> semantics.
449 * orig_ct in the byterange/multipart handling may not be
450 needed. Apache 1.3 just never stashed "multipart" into
451 r->content_type. We should probably follow suit since the
452 byterange stuff doesn't want the rest of the code to see the
453 multipart content-type; the other code should still think it is
454 dealing with the <orig_ct> stuff.
455 Status: Greg volunteers to investigate (esp. since he was most
456 likely the one to break it :-)
458 EXPERIMENTAL MODULES:
460 Experimental modules should eventually be be promoted to fully supported
461 status or removed from the repository entirely (ie, the
462 'experiment' failed). This section tracks what needs to happen to
463 get the modules promoted to fully supported status.