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