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