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