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