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