Patches considered for backport are noted in their branches' STATUS:
- * http://svn.apache.org/repos/asf/httpd/httpd/branches/1.3.x/STATUS
* http://svn.apache.org/repos/asf/httpd/httpd/branches/2.0.x/STATUS
* http://svn.apache.org/repos/asf/httpd/httpd/branches/2.2.x/STATUS
+
Release history:
[NOTE that x.{odd}.z versions are strictly Alpha/Beta releases,
while x.{even}.z versions are Stable/GA releases.]
- 2.3.5 : Tagged on January 21, 2010.
- 2.3.4 : Tagged on November 24, 2009.
+ 2.3.12 : In development.
+ 2.3.11 : Released as Beta on March 7, 2011.
+ 2.3.10 : Tagged on December 13, 2010. Released Dec 21, 2010.
+ 2.3.9 : Tagged on November 23, 2010, not released.
+ 2.3.8 : Tagged on August 24, 2010.
+ 2.3.7 : Tagged on August 19, 2010, not released.
+ 2.3.6 : Released on June 21, 2010.
+ 2.3.5 : Released on January 26, 2010.
+ 2.3.4 : Released on December 8, 2009.
2.3.3 : Tagged on November 11, 2009, not released.
2.3.2 : Tagged on March 23, 2009, not released.
2.3.1 : Tagged on January 2, 2009, not released.
* Open bugs in the bug database.
+ * See also the STATUS file in the docs/ directory, which lists documentation-specific TODO items.
+
CURRENT RELEASE NOTES:
+GA PLAN:
+
+ Jim proposes another beta release the end of March, another in
+ April with a goal towards GA in May (at the latest). Jim volunteers
+ to RM these.
+
RELEASE SHOWSTOPPERS:
+ FOR GA:
+
+ * Modules that are not ready for production use should be marked as
+ experimental or be removed. The same for modules without documentation.
+ Candidates:
+ - MPM simple
+ - mod_serf
+
+ * Review the example configuration. It should be based on current best
+ practices and not use deprecated features.
+
* Not all MPMs are updated to set conn_rec::current_thread correctly.
(Prefork, Worker, Event, Simple are updated).
+ jim sez: Then we just ship with those... mark any others as
+ experimental, pgollucci +1 jim
+
+ * The mod_session* modules need to be checked that their hooks respect
+ the returning of int (HTTP status codes) and apr_status_t as appropriate,
+ and any anomolies fixed.
+ jim sez: from what I can see, mod_session* is no worse that other
+ modules that mix these 2 types... clean up is
+ forthcoming but should not be considered a blocker, imo
+ pgollucci: +1 jim
+
+ * mod_ssl's proxy support only allows one proxy client certificate per
+ frontend virtual host. Lift this restriction.
+ jim sez: Why a blocker?, pgollucci +1 jim
+
+ FOR BETA:
+
+
+ OLD ISSUES THAT WERE THOUGHT TO BE SHOWSTOPPERS FOR 2.2 BUT OBVIOUSLY WEREN'T:
* Handling of non-trailing / config by non-default handler is broken
http://marc.theaimsgroup.com/?l=apache-httpd-dev&m=105451701628081&w=2
CURRENT VOTES:
- * If the parent process dies, should the remaining child processes
- "gracefully" self-terminate. Or maybe we should make it a runtime
- option, or have a concept of 2 parent processes (one being a
- "hot spare").
- See: Message-ID: <3C58232C.FE91F19F@Golux.Com>
-
- Self-destruct: Ken, Martin, Lars
- Not self-destruct: BrianP, Ian, Cliff, BillS
- Make it runtime configurable: Aaron, jim, Justin, wrowe, rederpj, nd
+ * Name the Server (version 2.4 or 3.0, depending on the final call)
+ Recent discussion indicates we should designate a (short name).
+ This is not yet a [Vote] - Your nominations please:
+ * Apache HTTP Server (httpd)
+ +1: sctemme (why mess with it?), pgollucci
- /* The below was a concept on *how* to handle the problem */
- Have 2 parents: +1: jim
- -1: Justin, wrowe, rederpj, nd, pgollucci
- +0: Lars, Martin (while standing by, could it do
- something useful?)
+RELEASE NON-SHOWSTOPPERS BUT WOULD BE REAL NICE TO WRAP THESE UP:
- * Make the worker MPM the default MPM for threaded Unix boxes.
- +1: Justin, Ian, Cliff, BillS, striker, wrowe, nd, pgollucci
- +0: BrianP, Aaron (mutex contention is looking better with the
- latest code, let's continue tuning and testing), rederpj, jim
- -0: Lars
+ * Clean up all the kruft and *extremely* outdated stuff below...
- pquerna: Do we want to change this for *2.4*?
- wrowe: Replies "yes"
+ * Maybe remove Limit/LimitExcept or at least make it log warnings when
+ mis-used.
-RELEASE NON-SHOWSTOPPERS BUT WOULD BE REAL NICE TO WRAP THESE UP:
+ * Sort out modules selections for most/all/reallyall. Maybe rename
+ all -> most, reallyall -> all, and remove the old 'most'.
* Patches submitted to the bug database:
http://issues.apache.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Apache+httpd-2&keywords=PatchAvailable
it, so that the server won't be slow down too much.
* RFC 2616 violations.
- Closed PRs: 15857.
- Open PRs: 15852, 15859, 15861, 15864, 15865, 15866, 15868, 15869,
- 15870, 16120, 16125, 16126, 16133, 16135, 16136, 16137,
- 16138, 16139, 16140, 16142, 16518, 16520, 16521,
+ Closed PRs: 15852, 15857, 15859, 15861, 15864, 15869, 15870, 16120,
+ 16125, 16135, 16136, 16137, 16138, 16139, 16140, 16518,
+ 16520, 49825
+ Open PRs: 15865, 15866, 15868, 16126, 16133, 16142, 16521, 42978
jerenkrantz says: need to decide how many we need to backport and/or
if these rise to showstopper status.
wrowe suggests: it would be nice to see "MUST" v.s. "SHOULD" v.s. "MAY"
out of this list, without reviewing them individually.
- * There is a bug in how we sort some hooks, at least the pre-config
- hook. The first time we call the hooks, they are in the correct
- order, but the second time, we don't sort them correctly. Currently,
- the modules/http/config.m4 file has been renamed to
- modules/http/config2.m4 to work around this problem, it should moved
- back when this is fixed.
-
- OtherBill offers that this is a SERIOUS problem. We do not sort
- correctly by the ordering arguments passed to the register hook
- functions. This was proven when I reordered the open_logs hook
- to attempt to open the error logs prior to the access logs. Possibly
- the entire sorting code needs to be refactored.
-
* pipes deadlock on all platforms with limited pipe buffers (e.g. both
Linux and Win32, as opposed to only Win32 on 1.3). The right solution
is either GStein's proposal for a "CGI Brigade", or OtherBill's proposal
chrisd: Has this been fixed by the changes for PR 38737?
- * --enable-mods-shared="foo1 foo2" is busted on Darwin. Pier
- posted a patch (Message-ID: <B8DBBE8D.575A%pier@betaversion.org>).
-
* We do not properly substitute the prefix-variables in the configuration
scripts or generated-configs. (i.e. if sysconfdir is etc,
httpd-std.conf points to conf.)
the ja-jis encoding.
* There is increasing demand from module writers for an API
- that will allow them to control the server à la apachectl.
+ that will allow them to control the server à la apachectl.
Reasons include sole-function servers that need to die if
an external dependency (e.g., a database) fails, et cetera.
Perhaps something in the (ever more abused) scoreboard?
* Do we need SSL_set_read_ahead()?
- * the ssl_expr api is NOT THREAD SAFE. race conditions exist:
- -in ssl_expr_comp() if SSLRequire is used in .htaccess
- (ssl_expr_info is global)
- -is ssl_expr_eval() if there is an error
- (ssl_expr_error is global)
-
* SSLRequire directive (parsing of) leaks memory
* Diffie-Hellman-Parameters for temporary keys are hardcoded in
* mod_cache: Handle ESI tags.
- * mod_cache: Resolve issue of how to cache page fragements (or perhaps
- -if- we want to cache page fragements). Today, mod_cache/mod_mem_cache
+ * mod_cache: Resolve issue of how to cache page fragments (or perhaps
+ -if- we want to cache page fragments). Today, mod_cache/mod_mem_cache
will cache #include 'virtual' requests (but not #include 'file'
requests). This was accomplished by making CACHE_IN a
CONTENT_SET-1 filter to force it to run before the SUBREQ_CORE
line server hooks (Ryan really hated this. It is great for
performance, but bad because of the complications listed above).
- mod_cache/mod_mem_cache/mod_disk_cache:
+ mod_cache/mod_mem_cache/mod_cache_disk:
* mod_mem_cache: Consider adding a RevalidateTimeout directive to
specify time at which local cached content is to be revalidated
jerenkrantz says: Too slow. Get regexs away from speedy caches by
default. Introduce a new CacheEnableRegex if you want.
- * mod_mem_cache/mod_disk_cache: Need to be able to query cache
+ * mod_mem_cache/mod_cache_disk: Need to be able to query cache
status (num of entries, cache object properties, etc.).
mod_status could be extended to query optional hooks defined
by modules for the purpose of reporting module status.
HTTP or SNMP?
jerenkrantz says: Yawn. Who cares.
- * MaxRequestsPerChild measures connections, not requests.
- Until someone has a better way, we'll probably just rename it
- "MaxConnectionsPerChild".
-
* Regex containers don't work in an intutive way
Status: No one has come up with an efficient way to fix this
behavior. Dean has suggested getting rid of regex containers
'experiment' failed). This section tracks what needs to happen to
get the modules promoted to fully supported status.
+
projects / apache / blobdiff