1 APACHE 2.5 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 separately 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
17 Patches considered for backport are noted in their branches' STATUS:
19 * http://svn.apache.org/repos/asf/httpd/httpd/branches/2.0.x/STATUS
20 * http://svn.apache.org/repos/asf/httpd/httpd/branches/2.2.x/STATUS
21 * http://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.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.5.0 : In Development.
31 Contributors looking for a mission:
33 * Just do an egrep on "TODO" or "XXX" in the source.
35 * Review the bug database at: http://issues.apache.org/bugzilla/
37 * Review the "PatchAvailable" bugs in the bug database:
39 https://issues.apache.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Apache+httpd-2&keywords=PatchAvailable
41 After testing, you can append a comment saying "Reviewed and tested".
43 * Open bugs in the bug database.
45 * See also the STATUS file in the docs/ directory, which lists documentation-specific TODO items.
48 CURRENT RELEASE NOTES:
53 THINGS THAT SHOULD BE CONSIDERED EARLY IN THE 2.6/3.0 DEVELOPMENT CYCLE:
55 * Change default prefix from /usr/local/apache2 to something corresponding
56 to the project name. Rename apachectl.
58 * Change merge order of <Location> to be most specific match last. This
59 is more consistent with <Directory> and allows some optimizations for the
62 * Detect Lua 5.2.0 during configure and add LUA_COMPAT_ALL to CPPFLAGS.
63 Maybe it even suffices to add LUA_COMPAT_MODULE and individually
64 care about the two remaining incompatible code lines (one with lua_strlen,
67 OLD ISSUES THAT WERE THOUGHT TO BE SHOWSTOPPERS FOR 2.4 BUT OBVIOUSLY WEREN'T:
69 * Handling of non-trailing / config by non-default handler is broken
70 http://marc.theaimsgroup.com/?l=apache-httpd-dev&m=105451701628081&w=2
71 jerenkrantz asks: Why should this block a release?
72 wsanchez agrees: this may be a change in behavior, but isn't
73 clearly wrong, and even if so, it doesn't seem like a
76 * the edge connection filter cannot be removed
77 http://marc.theaimsgroup.com/?l=apache-httpd-dev&m=105366252619530&w=2
78 http://mail-archives.apache.org/mod_mbox/httpd-dev/200501.mbox/%3C41E30B42.4060202@stason.org%3E
80 jerenkrantz asks: Why should this block a release?
82 stas replies: because it requires a rewrite of the filters stack
83 implementation (you have suggested that) and once 2.2 is
84 released you can't do that anymore.
86 pgollucci: this affects mod_perl I'm pretty sure.
90 * Name the Server (version 2.4 or 3.0, depending on the final call)
91 Recent discussion indicates we should designate a (short name).
92 This is not yet a [Vote] - Your nominations please:
93 * Apache HTTP Server (httpd)
94 +1: sctemme (why mess with it?), pgollucci
96 RELEASE NON-SHOWSTOPPERS BUT WOULD BE REAL NICE TO WRAP THESE UP:
98 * Clean up all the kruft and *extremely* outdated stuff below...
100 * Maybe remove Limit/LimitExcept or at least make it log warnings when
103 * Patches submitted to the bug database:
104 http://issues.apache.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Apache+httpd-2&keywords=PatchAvailable
106 * Filter stacks and subrequests, redirects and fast redirects.
107 There's at least one PR that suffers from the current unclean behaviour
108 (which lets the server send garbage): PR 17629
109 nd says: Every subrequest should get its own filter stack with the
110 subreq_core filter as bottom-most. That filter does two things:
111 - swallow EOS buckets
112 - redirect the data stream to the upper request's (rr->main)
113 filter chain directly after the subrequest's starting
115 Once we have a clean solution, we can try to optimize
116 it, so that the server won't be slow down too much.
118 * RFC 2616 violations.
119 Closed PRs: 15852, 15857, 15859, 15861, 15864, 15869, 15870, 16120,
120 16125, 16135, 16136, 16137, 16138, 16139, 16140, 16518,
122 Open PRs: 15865, 15866, 15868, 16126, 16133, 16142, 16521, 42978
123 jerenkrantz says: need to decide how many we need to backport and/or
124 if these rise to showstopper status.
125 wrowe suggests: it would be nice to see "MUST" v.s. "SHOULD" v.s. "MAY"
126 out of this list, without reviewing them individually.
128 * pipes deadlock on all platforms with limited pipe buffers (e.g. both
129 Linux and Win32, as opposed to only Win32 on 1.3). The right solution
130 is either GStein's proposal for a "CGI Brigade", or OtherBill's proposal
131 for "Poll Buckets" for "Polling Filter Chains". Or maybe both :-)
133 * All handlers should always send content down even if r->header_only
134 is set. If not, it means that the HEAD requests don't generate the
135 same headers as a GET which is wrong.
137 * exec cmd and suexec arg-passing enhancements
138 Status: Patches proposed
139 Message-ID: <20020526041748.A29148@prodigy.Redbrick.DCU.IE>
140 (see the "proc.patch" and "suexec-shell.patch" links in this message)
142 * The 2.0.36 worker MPM graceless shutdown changes work but are
143 a bit clunky on some platforms; eg, on Linux, the loop to
144 join each worker thread seems to hang, and the parent ends up
145 killing off the child with SIGKILL. But at least it shuts down.
147 chrisd: Has this been fixed by the changes for PR 38737?
149 * We do not properly substitute the prefix-variables in the configuration
150 scripts or generated-configs. (i.e. if sysconfdir is etc,
151 httpd-std.conf points to conf.)
153 * If any request gets through ap_process_request_internal() and is
154 scheduled to be served by the core handler, without a flag that this
155 r->filename was tested by dir/file_walk, we need to 500 at the very
156 end of the ap_process_request_internal() processing so sub_req-esters
157 know this request cannot be run. This provides authors of older
158 modules better compatibility, while still improving the security and
161 Status: still need to decide where this goes, OtherBill comments...
162 Message-ID: <065701c14526$495203b0$96c0b0d0@roweclan.net>
163 [Deleted comments regarding the ap_run_handler phase, as irrelevant
164 as BillS points out that "common case will be caught in
165 default_handler already (with the r->finfo.filetype == 0 check)"
166 and the issue is detecting this -before- we try to run the req.]
168 gregames says: can this happen somehow without a broken module
169 being involved? If not, why waste cycles trying to defend against
170 potential broken modules? It seems futile.
171 wrowe counters: no, it shouldn't happen unless the module is broken.
172 But the right answer is to fail the request up-front in dir/file
173 walk if the path was entirely invalid; and we can't do that either
174 UNTIL 2.1 or we break modules that haven't hooked map_to_storage.
176 * Can a static httpd be built reliably?
177 Message-ID: <20020207142751.T31582@clove.org>
179 * Usage of APR_BRIGADE_NORMALIZE in core_input_filter should be
182 <Pine.LNX.4.33.0201202232430.318-100000@deepthought.cs.virginia.edu>
183 Jeff wonders if we still care about this. It is no longer an
184 API issue but simply an extra trip through the brigade.
186 * Try to get libtool inter-library dependency code working on AIX.
187 Message-ID: <cm3n10lx555.fsf@rdu163-40-092.nc.rr.com>
189 Justin says: If we get it working on AIX, we can enable this
190 on all platforms and clean up our build system somewhat.
191 Jeff says: I thought I tested a patch for you sometime in
192 January that you were going to commit within a few days.
194 * Handling of %2f in URIs. Currently both 1.3 and 2.0
195 completely disallow %2f in the request URI path (see
196 ap_unescape_url() in util.c). It's permitted and passed
197 through in the query string, however. Roy says the
198 original reason for disallowing it, from five years ago,
199 was to protect CGI scripts that applied PATH_INFO to
200 a filesystem location and which might be tricked by
201 ..%2f..%2f(...). We *should* allow path-info of the
202 form 'http://foo.com/index.cgi/path/to/path%2finfo'.
203 Since we've revamped a lot of our processing of path
204 segments, it would be nice to allow this, or at least
205 allow it conditionally with a directive.
207 OtherBill adds that %2f as the SECOND character of a multibyte
208 sequence causes the request to fail! This happens notably in
211 * There is increasing demand from module writers for an API
212 that will allow them to control the server à la apachectl.
213 Reasons include sole-function servers that need to die if
214 an external dependency (e.g., a database) fails, et cetera.
215 Perhaps something in the (ever more abused) scoreboard?
217 On the other hand, we already have a pipe that goes between parent
218 and child for graceful shutdown events, along with an API that
219 can be used to send a message down that pipe. In threaded MPMs,
220 it is easy enough to make that one pipe be used for graceful
221 and graceless events, and it is also easy to open that pipe
222 to both parent and child for writing. Then we just need to
223 figure out how to do graceless on non-threaded MPMs.
225 * Allow the DocumentRoot directive within <Location > scopes? This
226 allows the beloved (crusty) Alias /foo/ /somepath/foo/ followed
227 by a <Directory /somepath/foo> to become simply
228 <Location /foo/> DocumentRoot /somefile/foo (IMHO a bit more legible
229 and in-your-face.) DocumentRoot unset would be accepted [and would
230 not permit content to be served, only virtual resources such as
231 server-info or server-status.
232 This proposed change would _not_ depricate Alias.
233 striker: See the thread starting with Message-ID:
234 JLEGKKNELMHCJPNMOKHOGEEJFBAA.striker@apache.org.
236 * Win32: Rotatelogs sometimes is not terminated when Apache
237 goes down hard. FirstBill was looking at possibly tracking the
238 child's-child processes in the parent process.
239 stoddard: Shared scoreboard might offer a good way for the parent
240 to keep track of 'other child' processes and whack them if the child
242 Other thoughts on walking the process chain using the NT kernel
243 have also been proposed on APR.
245 * Eliminate unnecessary creation of pipes in mod_cgid
247 * Combine log_child and piped_log_spawn. Clean up http_log.c.
250 * Platforms that do not support fork (primarily Win32 and AS/400)
251 Architect start-up code that avoids initializing all the modules
252 in the parent process on platforms that do not support fork.
254 * There are still a number of places in the code where we are
255 losing error status (i.e. throwing away the error returned by a
256 system call and replacing it with a generic error code)
258 * Mass vhosting version of suEXEC.
260 * All DBMs suffer from confusion in support/dbmmanage (perl script) since
261 the dbmmanage employs the first-matched dbm format. This is not
262 necessarily the library that Apache was built with. Aught to
263 rewrite dbmmanage upon installation to bin/ with the proper library
264 for predictable mod_auth_dbm administration.
265 Questions; htdbm exists, time to kill dbmmanage, or does it remain
266 useful as a perl dbm management example? If we keep it,
267 do we address the issue above?
270 Some additional items remaining:
271 - case_preserved_filename stuff
272 (use the new canonical name stuff?)
273 - find a new home for ap_text(_header)
274 - is it possible to remove the DAV: namespace stuff from util_xml?
276 * ap_core_translate() and its use by mod_mmap_static and mod_file_cache
277 are a bit wonky. The function should probably be exposed as a utility
278 function (such as ap_translate_url2fs() or ap_validate_fs_url() or
279 something). Another approach would be a new hook phase after
280 "translate" which would allow the module to munge what the
281 translation has decided to do.
282 Status: Greg +1 (volunteers)
284 * Explore use of a post-config hook for the code in http_main.c which
285 calls ap_fixup_virutal_hosts(), ap_fini_vhost_config(), and
286 ap_sort_hooks() [to reduce the logic in main()]
288 * read the config tree just once, and process N times (as necessary)
290 * (possibly) use UUIDs in mod_unique_id and/or mod_usertrack
292 * (possibly) port the bug fix for PR 6942 (segv when LoadModule is put
293 into a VirtualHost container) to 2.0.
295 * shift stuff to mod_core.h
297 * callers of ap_run_create_request() should check the return value
298 for failure (Doug volunteers)
300 * Fix the worker MPM to use POD to kill child processes instead
301 of ap_os_killpg, regardless of how they should die.
303 chrisd: Is this done, by any chance? See r92598 and r93358.
305 * Scoreboard structures could be changed in the future such that
306 proper alignment is not maintained, leading to segfaults on
307 some systems. Cliff posted a patch to deal with this issue but
308 later recanted. See this message to dev@apr.apache.org:
310 <Pine.LNX.4.44.0203011354090.16457-200000@deepthought.cs.virginia.edu>
312 * APXS either needs to be fixed completely for use when apr is out of tree,
313 or it should drop query mode altogether, and we just grow an
314 httpd-config or similar arrangement.
315 To quote a discussion in STATUS earlier:
317 thommay: this doesn't fix all the problems with apxs and out of
318 tree apr/apr-util, but it's a good start. There's still the
319 query cases; but I'm beginning to think that in these cases
320 the app should be querying ap{r,u}-config directly
321 deprecate -q: add htpd-config: gstein, pquerna, minfrin, pgollucci
324 TODO ISSUES REMAINING IN MOD_SSL:
326 * SSLRequire directive (parsing of) leaks memory
328 * ssl_var_lookup could be rewritten to be MUCH faster
331 * mod_proxy: Ability to run SSL over proxy gateway connections,
332 encrypting (or reencrypting) at the proxy.
334 * mod_cache: Handle ESI tags.
336 * mod_cache: Resolve issue of how to cache page fragments (or perhaps
337 -if- we want to cache page fragments). Today, mod_cache/mod_mem_cache
338 will cache #include 'virtual' requests (but not #include 'file'
339 requests). This was accomplished by making CACHE_IN a
340 CONTENT_SET-1 filter to force it to run before the SUBREQ_CORE
341 filter. But now responses cannot be cached that include the
342 effects of having been run through CONTENT_SET filters
343 (mod_deflate, mod_expires, etc). We could rerun all the
344 CONTENT_SET filters on the cached response, but this will not
345 work in all cases. For example, mod_expires relies on installing
346 the EXPIRATION filter during fixups. Contents served out of
347 mod_cache (out of the quick_handler) bypass -all- the request
348 line server hooks (Ryan really hated this. It is great for
349 performance, but bad because of the complications listed above).
351 mod_cache/mod_mem_cache/mod_cache_disk:
353 * mod_mem_cache: Consider adding a RevalidateTimeout directive to
354 specify time at which local cached content is to be revalidated
355 (ie, underlying file stat'ed to see if it has changed).
357 * mod_mem_cache/mod_cache_disk: Need to be able to query cache
358 status (num of entries, cache object properties, etc.).
359 mod_status could be extended to query optional hooks defined
360 by modules for the purpose of reporting module status.
361 mod_cache (et. al.) could define optional hooks that are called
362 to collect status. Status should be queryable by
364 jerenkrantz says: Yawn. Who cares.
366 * Regex containers don't work in an intutive way
367 Status: No one has come up with an efficient way to fix this
368 behavior. Dean has suggested getting rid of regex containers
370 OtherBill suggests: We at least seem to agree on eliminating
371 the <Container ~ foo> forms, and using only
372 <ContainerMatch foo> semantics.
374 * orig_ct in the byterange/multipart handling may not be
375 needed. Apache 1.3 just never stashed "multipart" into
376 r->content_type. We should probably follow suit since the
377 byterange stuff doesn't want the rest of the code to see the
378 multipart content-type; the other code should still think it is
379 dealing with the <orig_ct> stuff.
380 Status: Greg volunteers to investigate (esp. since he was most
381 likely the one to break it :-)
383 EXPERIMENTAL MODULES:
385 Experimental modules should eventually be be promoted to fully supported
386 status or removed from the repository entirely (ie, the
387 'experiment' failed). This section tracks what needs to happen to
388 get the modules promoted to fully supported status.