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