Re: apache freebsd port --enable-so
On Tue, Jul 23, 2002 at 11:43:54PM +0100, Dev Zero G Ltd wrote: How can I make make compile/configure/make apache 2 with the --enable-so option? I can not run ./configure since I already have a Makefile. If you are using the FreeBSD port then it does --enable-so by default. Tony. -- f.a.n.finch [EMAIL PROTECTED] http://dotat.at/ DOGGER: WEST OR NORTHWEST 4 OR 5, OCCASIONALLY 6 AT FIRST. SHOWERS THEN RAIN. GOOD BECOMING MODERATE.
[VOTE] httpd-std.conf WAS: RE: daedalus is running httpd-2.0.pre40
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Jeff Trawick
Sent: 23 July 2002 19:30
[...]
I'm curious about how other people feel about this, so I started a
vote in STATUS.
* httpd-std.conf and friends
a) httpd-std.conf should be tailored by install (from src or
binbuild) even if user has existing httpd.conf
+1: trawick, slive, gregames, ianh
In the build tree? If yes, then sure.
b) tailored httpd-std.conf should be copied by install to
sysconfdir/examples
+1: trawick
-0: striker
Installing in ${sysconfdir} or a subdir thereof is in my opinion not
an option. If users go through the effort of keeping their config
directory clean, we shouldn't clutter it when they reinstall/upgrade
apache.
c) tailored httpd-std.conf should be installed to
sysconfdir/examples or manualdir/exampleconf/
+1: slive
Having an example config in the manual seems like a decent idea.
d) Installing a set of default config files when upgrading a server
doesn't make ANY sense at all.
+1: rbb, striker
ianh - medium/big sites don't use 'standard config' anyway, as it
usually needs major customizations
Exactly, why should users that keep their config dir clean have to pay when
some users don't want to be troubled with getting httpd-std.conf from elsewhere
and need it installed at their fingertips?
Secondly consider that you have installed 2.0.35 and are upgrading to 2.0.40.
If ${sysconfdir}/[examples/]httpd-std.conf would be overwritten, you would have
no chance to compare the old httpd-std.conf with the new httpd-std.conf anymore.
I consider that diff more usefull than the diff between httpd.conf and the new
httpd-std.conf.
Sander
Re: Envariables for logging phase only
Joshua Slive wrote:
On Tue, 23 Jul 2002, Rodent of Unusual Size wrote:
I personally find that a bit baroque. :-) Also, it's tied
specifically to mod_log_config. However, you've given me
an idea, so here's a counterproposal:
LogStatus envname[=val] statusre ...
(I think the envname should be last to align with SetEnvIf.)
I didn't do it that way so that multiple status codes could be
specified, a la AddType and friends.
I'm still in blue sky mode, so feel free to ignore me (as usual ;-), but
if you're going to do that, why not go all the way:
LogVariable %s 40[0-9] exclude
LogVariable %a 127\.0\.0\.1 exclude
LogVariable %U \.jpg exclude
LogVariable %{Referer}i yahoo.com exclude
Customlog ... env=!exclude
Where the first argument is a log-format %-directive, the second is a
regex, and the third is an environment variable. I would think that this
should be relatively easy to do given the way mod_log_config works in 2.0.
Fine and cool -- except that this is mod_log_config specific, and it
would be nice to have something that was module-neutral. Or are the
logging format effectors dissociated from mod_log_config and moved into
the core now? I haven't kept up there..
And yes, I'm still a big proponent of not using conditional logging at
all; log everything and postprocess to get rid of what you don't want.
If you could, would you have your mail server reject spam on detection?
Or continue to accept *everything* and filter out even known spam after
the fact? (Actually, I think you *can* teach sendmail to reject spam
using milters..) Regardless, there are those (and I'm among them) who
think that conditional logging is more efficient and the best way of
doing some things. It's in there, so let's not have this philosophical
discussion again.. :-)
--
#kenP-)}
Ken Coar, Sanagendamgagwedweinini http://Golux.Com/coar/
Author, developer, opinionist http://Apache-Server.Com/
Millennium hand and shrimp!
Re: cvs commit: httpd-2.0 STATUS
* Jeff Trawick ([EMAIL PROTECTED]) wrote : Thom May [EMAIL PROTECTED] writes: * James Cox ([EMAIL PROTECTED]) wrote : no! no! leave apachectl to behave as it always has done. could someone consider vetoing this argument based on backwards compatibility? -- James Agreed - why do we need this many layers of indirection? what does it buy us having apachectl call a script that calls httpd? To me it sucks that apachectl is more than an init script interface (i.e., that you need to do apachectl -V in some circumstances because there is no other shell script to set things up correctly). On the other hand, there is suckage associated with an extra layer of indirection between apachectl and httpd. Especially since most distributions of apache i've seen do this: /etc/init.d/apache - apachectl - httpd With the current proposal, this would turn into: /etc/init.d/apache - apachectl - httpd.sh - httpd which seems absurd. Could we, instead: provide an init.d style script ourselves, that just calls apachectl. Then let apachectl do all the leg work. This doesn't change current behaviour, but also provides a lightweight script for those who want it... Cheers, -Thom -- Thom May - [EMAIL PROTECTED] Overfiend Lords and squires, Overfiend Were you aware of the fact that you could increaseth the size of your penis by as much as half a cubit? Come visit the apothecary and essay the new miracle tonic by Dr. Goodfellow! You'll have all the fair maidens screaming, 'Good Knight!'
Support for win9x. What is required? Request for information.
I would like to roll out some software to users based on apache2 under windows 98 (and other windows +platforms). When visiting http://httpd.apache.org/docs-2.0/platform/windows.html I see a severe sounding message +stating that support for windows 98 is incomplete. What determines if the support is complete? I found reference to the lack of 98 support in the status file in the root of the distribution. There+are a couple of bugs there. Are there more? I had a look in the apache bug database for bugs +relating to windows 9x and httpd 2.0.39 and HEAD. The criteria were quite broad, but +I only found +one, bug 10435. I tried again including resolved, verified and closed bugs and +broadening the +criteria. I found thirty, twenty-five of which were flagged as duplicates. Of the +remaining five, +four were resolved or closed. Superficially, it looks like there's not too much work to be done to get the server ready for 9x. Is +this so? If not what's stopping it? Is there no one to do rigorous testing, for +example? I'll go and read through that bug list in detail now. Comments appreciated. (apologies if this is a double post) Russell
Re: [VOTE] httpd-std.conf WAS: RE: daedalus is running httpd-2.0.pre40
Secondly consider that you have installed 2.0.35 and are upgrading to 2.0.40.
If ${sysconfdir}/[examples/]httpd-std.conf would be overwritten, you would
have
no chance to compare the old httpd-std.conf with the new httpd-std.conf
anymore.
I consider that diff more usefull than the diff between httpd.conf and the new
httpd-std.conf.
True. But this problem could be solved by appending the version number to
the filename. httpd-std-2.0.36.conf and so on. So you'd get a nice
collection of various standard conf files in your
examples/templates/whatever directory.
(then we'd only need +VersionSort for our favorite file manager;-)
j.
--
Why did Nature create man? Was it to show that she is big enough to
make mistakes, or was it pure ignorance? -- Holbrook Jackson
- http://jgcl.at/ - new photos from summer camp 2002 in Moosen/Tirol
atol
There are several places in HTTPD where we use atol to parse ranges from HTTP headers. Problem (at least on Darwin) is that a long is smaller than size_t, and we're unable to handle large files in the 2-4GB range. atol is the same as calling strtol with NULL and 10 as the last to args, and we can use strtoll instead, so this is an easy fix, except than strtoll may not be on all of our platforms, so this seems like a job for APR, lest we have #ifdef HAVE_STRTOLL all over the place. The patch I got from Shantonu adds an APR function apr_atoll which returns a long long. It uses strtoll is available, otherwise falls back to strtol. Questions: 1- Is adding apr_strtoll kosher? 2- Should I also add apr_strtoll for completeness? -wsv
Re: [Win32] Compiling error missing apr-iconv.h
[EMAIL PROTECTED] (Juergen Heckel) writes: cvs login: failed to open c:/.cvspass for reading: No such file or directory Hi, I solved this problem:-) I created an empty file .cvspass on c:\ and now I could download all apr-iconv files. cool... I hit that cvs bug before too :) -- Jeff Trawick | [EMAIL PROTECTED] Born in Roswell... married an alien...
Re: [VOTE] httpd-std.conf WAS: RE: daedalus is running httpd-2.0.pre40
Sander Striker wrote:
Exactly, why should users that keep their config dir clean have to pay when
some users don't want to be troubled with getting httpd-std.conf from elsewhere
and need it installed at their fingertips?
Getting the defaults from elsewhere doesn't bother me if the dir has a decent
name.
Secondly consider that you have installed 2.0.35 and are upgrading to 2.0.40.
If ${sysconfdir}/[examples/]httpd-std.conf would be overwritten, you would have
no chance to compare the old httpd-std.conf with the new httpd-std.conf anymore.
I consider that diff more usefull than the diff between httpd.conf and the new
httpd-std.conf.
Agreed. diff'ing the defaults would be simple if we always installed them
somewhere, then copied them to conf/ only when conf/ is created.
johannes m. richter wrote:
True. But this problem could be solved by appending the version number to
the filename. httpd-std-2.0.36.conf and so on. So you'd get a nice
collection of various standard conf files in your
examples/templates/whatever directory.
Sorry, but the thought of an ever-growing collection of files doesn't seem very
nice to me. You can rename them if you really want this.
Greg
Re: atol
On Wed, Jul 24, 2002 at 10:45:40AM -0400, Wilfredo Sanchez wrote: 1- Is adding apr_strtoll kosher? +1. 2- Should I also add apr_strtoll for completeness? +1. -- justin
Re: mysqlsupport for virtuals.
I wait for it.. / Jonas Hi Jonas, i'm actually workin on hacking a module for this. (ie, like mod_vhost_alias, but uses a db) give me maybe a few weeks and i'll publish.. -- james Hi My http.conf file grows every day and its getting big... It's getting hard to find anyting without seartching in it. My question is : I like to move all virtualshosts away from httpd.conf in to a mysql server. My doing that it would be muth easy to maintain my virtualhosts. Have someone tried this without loosing preformance?
Re: Query: bugs 8712 and 10156/NOW 10235 as well.
Larry Rosenman [EMAIL PROTECTED] writes: Can anyone tell me what I need to provide to get these 3 bugs looked at: 8712 need to modify apxs to add LoadModule/AddModule outside of IfXXX I thought somebody commented on this general problem recently. My guess is that there won't be a lot of desire to mess with this in 1.3 (my opinion only). 10156 How do GNU config.sub/config.guess represent Unixware 8+? Do they bite off on the re-brand to OpenUNIX? 10235 Too much in one PR (if there is an IPv6 problem *and* a DSO build problem you probably want separate PRs). Please update the PR to make the following clear: What is the exact failure with --enable-mods-shared=all? Are the modules built? Do they load? What exactly is the IPv6 failure? Did everything build? Was there a run-time failure? -- Jeff Trawick | [EMAIL PROTECTED] Born in Roswell... married an alien...
Re: Query: bugs 8712 and 10156/NOW 10235 as well.
On Wed, 2002-07-24 at 11:30, Jeff Trawick wrote: Larry Rosenman [EMAIL PROTECTED] writes: Can anyone tell me what I need to provide to get these 3 bugs looked at: 8712 need to modify apxs to add LoadModule/AddModule outside of IfXXX I thought somebody commented on this general problem recently. My guess is that there won't be a lot of desire to mess with this in 1.3 (my opinion only). I hope that some DOES fix it (at least for 2.0), but preferably for 1.3 10156 How do GNU config.sub/config.guess represent Unixware 8+? Do they bite off on the re-brand to OpenUNIX? The current GNU config.sub/config.guess show as sysv5OpenUNIX8.0.0 $ sh config.guess i686-unknown-sysv5OpenUNIX8.0.1 (I'm running a beta of 8.0.1, but same difference on 8.0.0). 10235 Too much in one PR (if there is an IPv6 problem *and* a DSO build problem you probably want separate PRs). Please update the PR to make the following clear: What is the exact failure with --enable-mods-shared=all? Are the modules built? Do they load? What exactly is the IPv6 failure? Did everything build? Was there a run-time failure? I thought I included full scripts I can make a shell account available. What more do I need to do. Basically, on this platform for now you need to ignore the IPv6 stuff, and not use it. (there is an API, but no protocol stack). -- Jeff Trawick | [EMAIL PROTECTED] Born in Roswell... married an alien... -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED] US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749
Re: Query: bugs 8712 and 10156/NOW 10235 as well.
Larry Rosenman [EMAIL PROTECTED] writes: 10156 I will plan to commit your patch in the next 24 hours. e-mail me directly if this doesn't happen. 10235 What is the exact failure with --enable-mods-shared=all? Are the modules built? Do they load? I thought I included full scripts I can make a shell account available. I see the failure to load mod_access now. I got frustrated by all the terminal control sequences at the end of your attachment. Is ap_get_remove_host exported from httpd? nm on httpd should be able to tell. You may need to axe the libtool --silent option (LTFLAGS=' ' ./configure ...), see how httpd and your DSOs are linked, and compare it with what a DSO build of Apache 1.3. Maybe your level of libtool is broken for your platform, maybe there is something that Apache needs to do special. What exactly is the IPv6 failure? Did everything build? Was there a run-time failure? Basically, on this platform for now you need to ignore the IPv6 stuff, and not use it. (there is an API, but no protocol stack). It is the same with many Linux boxes on which Apache works fine without disabling the IPv6 support. We don't choose to disable IPv6 in the build if the API is there. Does Apache fail without --disable-ipv6? Is there a symptom we can check for at configure time? We do check for certain broken APIs and disable it in that situation. Maybe there is another symptom we should check for. -- Jeff Trawick | [EMAIL PROTECTED] Born in Roswell... married an alien...
Re: HEAD is borked
David Reid wrote: Who's we? Oh, was this more IRC related conversations? IRC is cool for some things, but it can inadvertently conceal technical discussions which belong on the mailing lists and in the archives thereof -- for the benefit of both posterity and those who weren't on the channel. -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Golux.Com/coar/ Author, developer, opinionist http://Apache-Server.Com/ Millennium hand and shrimp!
RE: HEAD is borked
From: Rodent of Unusual Size [mailto:[EMAIL PROTECTED]] Sent: 24 July 2002 20:58 David Reid wrote: Who's we? Oh, was this more IRC related conversations? IRC is cool for some things, but it can inadvertently conceal technical discussions which belong on the mailing lists and in the archives thereof -- for the benefit of both posterity and those who weren't on the channel. The subject this was referring to wasn't discussed on irc at all. The 'we' part came from an external poster. Sander
Re: daedalus is running httpd-2.0.pre40
Ryan Bloom wrote: Why is that a good thing? Because it's consistent with how it works on ten million existing servers? :-) -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Golux.Com/coar/ Author, developer, opinionist http://Apache-Server.Com/ Millennium hand and shrimp!
Re: daedalus is running httpd-2.0.pre40
Ryan Bloom wrote: That is the difference between developers and users. I want the -std files on my DEVELOPER machines, and I have tricks to get them. I don't want them anywhere near my PRODUCTION machines, because they get in the way. You are hardly a typical user. You shouldn't think that what's good for Ryan-as-user is automatically good for *-as-user. I would be in favor of never installing them on an upgrade. They are useless on a production machine that already has a configuration. They are meant as DEFAULT values to help people get up and running. And they also provide examples of how things are done. When those things change on an upgrade -- such as adding the IfModule wrappers -- it makes excellent sense for them to be provided. Is there ANY other software package anywhere that actually re-installs the default configuration files on an upgrade? Stop handwaving. No-one is suggesting overwriting httpd.conf. And yes, *many* packages provide their defaults as part of an upgrade. Some even move the existing user config aside and put the new one in place. As an example, look for .rpmnew and .rpmsave files on a RH/MDK/... machine. -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Golux.Com/coar/ Author, developer, opinionist http://Apache-Server.Com/ Millennium hand and shrimp!
are downlevel manuals goodness?
If I'm reading the Makefile correctly, current HEAD no longer updates the manual/ directory if it exists, unlike 1.3. What good is a downlevel manual? Greg
Re: cvs commit: httpd-2.0/modules/mappers mod_negotiation.c
[EMAIL PROTECTED] writes: wsanchez2002/07/24 13:47:29 Modified:.CHANGES modules/dav/main mod_dav.c modules/experimental mod_cache.c modules/http http_protocol.c modules/mappers mod_negotiation.c Log: Replace atol() calls which should return long long with apr_atoll() calls. Submitted by: Shantonu Sen [EMAIL PROTECTED] Is there a way to avoid the 64-bit arithmetic where it isn't really needed? Aren't some anal compilers going to insist on telling us that it isn't good to store 64-bit values in 32-bit variables? Should we have something like apr_ato_off_t(), just as we have apr_off_t_toa()? apr_ato_off_t could map to apr_atoll() where necessary. -- Jeff Trawick | [EMAIL PROTECTED] Born in Roswell... married an alien...
Re: Command line argument inconsistency...
On Tue, Jul 23, 2002 at 11:43:03PM +0200, Martin Kraemer wrote: Yes. The unix philosophy. You are absolutely right: it IS inconsistent, and should be fixed. But rather than changing all exit codes to 1, I would prefer to see all these exit codes being changed to EX_OK: #define EX_OK 0 /* successful termination */ EXIT_SUCCESS and EXIT_FAILURE is the proper value. These should be defined by the system/compiler/whatever. -- justin
Re: are downlevel manuals goodness?
On Wed, Jul 24, 2002 at 04:58:55PM -0400, Greg Ames wrote: If I'm reading the Makefile correctly, current HEAD no longer updates the manual/ directory if it exists, unlike 1.3. What good is a downlevel manual? Yeah, that looks bogus. I'd move the copying of the manual to install-man and copy it unconditionally. -- justin
RE: are downlevel manuals goodness?
On Wed, Jul 24, 2002 at 04:58:55PM -0400, Greg Ames wrote: If I'm reading the Makefile correctly, current HEAD no longer updates the manual/ directory if it exists, unlike 1.3. What good is a downlevel manual? Yeah, that looks bogus. I'd move the copying of the manual to install-man and copy it unconditionally. -- justin kick me if i got this wrong, but manual was always copied into INSTDIR/html/manual right? that particularly sucked (i nuked html as one of the first things i did on install, so as not to confuse anything). what about sticking it into /usr/local/share or similar? and then having a built in link, such as server-status ? reason being, again, it'd be nice to make the INSTDIR cleaner. :) -- james
Re: are downlevel manuals goodness?
On Wed, Jul 24, 2002 at 11:11:48PM +0100, James Cox wrote: kick me if i got this wrong, but manual was always copied into INSTDIR/html/manual right? Nah, we switched it to go to $(prefix)/manual by default. It's not in the htdocs dir now. -- justin
Re: Command line argument inconsistency...
I decided that maybe I would take a different tac that is less intrusive on other platforms since this is a NetWare problem. If you look at os/netware/os.h you will see that we had already redefined exit() to call our pressanykey() function whenever the exit code is something other than 0. I added a global variable inside of our MPM that is set when our rewrite_args callback is called from main(). It is then unset when ap_mpm_run() is finally through all of the initialization and configuration stages. The thinking behind this is that if exit() is ever called during the initialization and configuration of the Apache process, we hold the screen open to display any error messages or information that has been printed to the screen. In addition, we also want to hold the screen open if exit() is ever called after that with an error code (which was the default case previously). But if Apache exits normally after the initialization and configuration stage is complete, we want the screen to auto-close. This way the only files I touch are os/netware/os.h and server/mpm/netware/mpm_netware.c. I'm not introducing a new #define that really has no meaning on any other platform other than NetWare. thanks, Brad Brad Nicholes Senior Software Engineer Novell, Inc., the leading provider of Net business solutions http://www.novell.com [EMAIL PROTECTED] Wednesday, July 24, 2002 3:33:11 PM On Tue, Jul 23, 2002 at 11:43:03PM +0200, Martin Kraemer wrote: Yes. The unix philosophy. You are absolutely right: it IS inconsistent, and should be fixed. But rather than changing all exit codes to 1, I would prefer to see all these exit codes being changed to EX_OK: #define EX_OK 0 /* successful termination */ EXIT_SUCCESS and EXIT_FAILURE is the proper value. These should be defined by the system/compiler/whatever. -- justin
[STATUS] (apache-1.3) Wed Jul 24 23:45:05 EDT 2002
APACHE 1.3 STATUS: -*-text-*- Last modified at [$Date: 2002/06/27 20:57:21 $] Release: 1.3.27-dev: In development 1.3.26: Tagged June 18, 2002. 1.3.25: Tagged June 17, 2002. Not released. 1.3.24: Tagged Mar 21, 2002. Announced Mar 22, 2002. 1.3.23: Tagged Jan 21, 2002. 1.3.22: Tagged Oct 8, 2001. Announced Oct 12, 2001. 1.3.21: Not released. (Pulled for htdocs/manual config mismatch. t/r Oct 5, 2001) 1.3.20: Tagged and rolled May 15, 2001. Announced May 21, 2001. 1.3.19: Tagged and rolled Feb 26, 2001. Announced Mar 01, 2001. 1.3.18: Tagged and rolled Not released. (Pulled because of an incorrect unescaping fix. t/r Feb 19, 2001) 1.3.17: Tagged and rolled Jan 26, 2001. Announced Jan 29, 2001. 1.3.16: Not released. (Pulled because of vhosting bug. t/r Jan 20, 2001) 1.3.15: Not released. (Pulled due to CVS dumping core during the tagging when it reached src/os/win32/) 1.3.14: Tagged and Rolled Oct 10, 2000. Released/announced on the 13th. 1.3.13: Not released. (Pulled in the first minutes due to a Netware build bug) 1.3.12: Tagged and rolled Feb. 23, 2000. Released/announced on the 25th. 1.3.11: Tagged and rolled Jan. 19, 2000. Released/announced on the 21st. 1.3.10: Not released. (Pulled at last minute due to a build bug in the MPE port) 1.3.9: Tagged and rolled on Aug. 16. Released and announced on 19th. 1.3.8: Not released. 1.3.7: Not released. 1.3.6: Tagged and rolled on Mar. 22. Released and announced on 24th. 1.3.5: Not released. 1.3.4: Tagged and rolled on Jan. 9. Released on 11th, announced on 12th. 1.3.3: Tagged and rolled on Oct. 7. Released on 9th, announced on 10th. 1.3.2: Tagged and rolled on Sep. 21. Announced and released on 23rd. 1.3.1: Tagged and rolled on July 19. Announced and released. 1.3.0: Tagged and rolled on June 1. Announced and released on the 6th. 2.0 : Available for general use, see httpd-2.0 repository RELEASE SHOWSTOPPERS: * Current vote on 2 PRs for inclusion: Bugz #9181 (Unable to set headers on non-2XX responses) +1: Martin, Jim Gnats #10246 (Add ProxyConnAllow directive) +0: Martin (or rather -.5, see dev@ Message [EMAIL PROTECTED]) RELEASE NON-SHOWSTOPPERS BUT WOULD BE REAL NICE TO WRAP THESE UP: * htpasswd.c and htdigest.c use tmpnam()... consider using mkstemp() when available. Message-ID: [EMAIL PROTECTED] Status: * Dean's unescaping hell (unescaping the various URI components at the right time and place, esp. unescaping the host name). Message-ID: [EMAIL PROTECTED] Status: * Martin observed a core dump because a ipaddr_chain struct contains a NULL-server pointer when being dereferenced by invoking httpd -S. Message-ID: [EMAIL PROTECTED] Status: Workaround enabled. Clean solution can come after 1.3.19 * long pathnames with many components and no AllowOverride None Workaround is to define Directory / with AllowOverride None, which is something all sites should do in any case. Status: Marc was looking at it. (Will asks 'wasn't this patched?') * Ronald Tschalär's patch to mod_proxy to allow other modules to set headers too (needed by mod_auth_digest) Message-ID: [EMAIL PROTECTED] Status: Available Patches (Most likely, will be ported to 2.0 as appropriate): * Backport of 2.0 ForceLanguagePriority directive /dist/httpd/contrib/patches/1.3/force_language_priority.patch Message-ID: [EMAIL PROTECTED] Status: * A rewrite of ap_unparse_uri_components() by Jeffrey W. Baker [EMAIL PROTECTED] to more fully close some segfault potential. Message-ID: Pine.LNX.4.21.0102102350060.6815-20@desktop Status: Jim +1 (for 1.3.19), Martin +0 * Andrew Ford's patch (1999/12/05) to add absolute times to mod_expires Message-ID: [EMAIL PROTECTED] Status: Martin +1, Jim +1, Ken +1 (on concept) * Raymond S Brand's path to mod_autoindex to fix the header/readme include processing so the envariables are correct for the included documents. (Actually, there are two variants in the patch message, for two different ways of doing it.) Message-ID: [EMAIL PROTECTED] Status: Martin +1(concept) * Jayaram's patch (10/27/99) for bugfix to mod_autoindex IndexIgnore file-extension should hide the files with this file- extension in directory listings. This was NOT happening because the total filename was being compared with the file-extension. Status: Martin +1(untested), Ken +1(untested) * Salvador Ortiz Garcia [EMAIL PROTECTED]' patch to allow DirectoryIndex to refer to URIs for non-static resources.
[STATUS] (httpd-2.0) Wed Jul 24 23:45:09 EDT 2002
APACHE 2.0 STATUS: -*-text-*- Last modified at [$Date: 2002/07/24 16:55:45 $] Release: 2.0.40 : in development. 2.0.39 : rolled June 17, 2002. 2.0.38 : rolled June 16, 2002. not released. 2.0.37 : rolled June 11, 2002. not released. 2.0.36 : released May 6, 2002 as GA. 2.0.35 : released April 5, 2002 as GA. 2.0.34 : tagged March 26, 2002. 2.0.33 : tagged March 6, 2002. not released. 2.0.32 : released Feburary 16, 2002 as beta. 2.0.31 : rolled Feburary 1, 2002. not released. 2.0.30 : tagged January 8, 2002. not rolled. 2.0.29 : tagged November 27, 2001. not rolled. 2.0.28 : released November 13, 2001 as beta. 2.0.27 : rolled November 6, 2001 2.0.26 : tagged October 16, 2001. not rolled. 2.0.25 : rolled August 29, 2001 2.0.24 : rolled August 18, 2001 2.0.23 : rolled August 9, 2001 2.0.22 : rolled July 29, 2001 2.0.21 : rolled July 20, 2001 2.0.20 : rolled July 8, 2001 2.0.19 : rolled June 27, 2001 2.0.18 : rolled May 18, 2001 2.0.17 : rolled April 17, 2001 2.0.16 : rolled April 4, 2001 2.0.15 : rolled March 21, 2001 2.0.14 : rolled March 7, 2001 2.0a9 : released December 12, 2000 2.0a8 : released November 20, 2000 2.0a7 : released October 8, 2000 2.0a6 : released August 18, 2000 2.0a5 : released August 4, 2000 2.0a4 : released June 7, 2000 2.0a3 : released April 28, 2000 2.0a2 : released March 31, 2000 2.0a1 : released March 10, 2000 Please consult the following STATUS files for information on related projects: * srclib/apr/STATUS * srclib/apr-util/STATUS * docs/STATUS CURRENT RELEASE NOTES: RELEASE SHOWSTOPPERS: * apr_poll() grows the pool (e.g., pchild or the thread's pool) on each call... Apache MPMs don't have logic to work around this issue. CURRENT VOTES: * httpd-std.conf and friends a) httpd-std.conf should be tailored by install (from src or binbuild) even if user has existing httpd.conf +1: trawick, slive, gregames, ianh, Ken b) tailored httpd-std.conf should be copied by install to sysconfdir/examples -0: striker c) tailored httpd-std.conf should be installed to sysconfdir/examples or manualdir/exampleconf/ +1: slive, trawick, Ken d) Installing a set of default config files when upgrading a server doesn't make ANY sense at all. +1: rbb, striker ianh - medium/big sites don't use 'standard config' anyway, as it usually needs major customizations -1: Ken * Should we always build [support*] binaries statically unless otherwise indicated? Message-ID: [EMAIL PROTECTED] +1: Ken, *wrowe [they are PITAs on OSX] -1: Justin, Ian * 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: [EMAIL PROTECTED] Self-destruct: Ken, Martin Not self-destruct: BrianP, Ian, Cliff, BillS Make it runtime configurable: Aaron, Jim, Justin Have 2 parents: +1: Jim -1: Justin, wrowe [for 2.0] +0: Martin (while standing by, could it do something useful?) * Make the worker MPM the default MPM for threaded Unix boxes. +1: Justin, Ian, Cliff, BillS, striker +0: BrianP, Aaron (mutex contention is looking better with the latest code, let's continue tuning and testing) -0: Lars RELEASE NON-SHOWSTOPPERS BUT WOULD BE REAL NICE TO WRAP THESE UP: * All handlers should always send content down even if r-header_only is set. If not, it means that the HEAD requests don't generate the same headers as a GET which is wrong. Is this a showstopper? +1: Justin, Ken -1: Aaron * server pushed CGI's not working. (Is this a showstopper??) PR: 8482 Message-ID: [EMAIL PROTECTED] * HP/UX 10.20: compile breakage in APR. Looks like it should be easy to fix, probably just some extraneous #include's that are fouling things up. PR: 9457 Jeff: See my reply and patch in the PR (and previous commit to stop using pipe as a field name). If patch is committed, we should be okay. I'll wait to see if the user tests the patch. Update by Jeff 20020722: I got an account on HP 10.20. It looks like some of the APR thread detection is screwed up. If we find pthread.h but we can't compile the pthread test program we still think we can use threads. For that reason, the patch I posted to the PR won't work as-is since a failed compile of the test
