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