Re: [PATCH] Remove Port from httpd.conf
On Mon, 10 Mar 2003, Rich Bowen wrote: I was under the impression that Port was necessary in some situations, in just the same way as ServerName. For example, if you accept requests on many ports, but you always want to issue redirects to one particular port. This is not the case in practice. On my servers, I tend to run stuff on several ports - for testing purposes or whatnot - and I never use Port in my configurations, just Listen. However, I also always have UseCanonicalName Off, so I may be just a little confused here too. I'll experiment some more with this, and get back to you. It's an issue when the server runs on a high port (say 127.0.0.1:8000), but users access it on port routable ip:80 (and then forwarded by the kernel or a front end proxy). Without the port statement, self referencing redirects (say from /dir to /dir/) will go out with port 8000 on them. - ask -- ask bjoern hansen, http://www.askbjoernhansen.com/ !try; do();
Re: snapshots not deleted
On Wed, 26 Feb 2003, Günter Knauf wrote: have just seen that the automatically generated snapshots are not deleted anymore since Feb-03... if this is wanted just ignore this post... I think this has been fixed. Or did you mean something else than the snapshots at http://cvs.apache.org/snapshots/httpd-2.0/ ? - ask -- ask bjoern hansen, http://www.askbjoernhansen.com/ !try; do();
Re: 2.1 Fallout; httpd v.s. httpd-2.0
On Mon, 25 Nov 2002, Wilfredo Sanchez wrote: [...] I don't really buy this performance noise about branches. In Darwin CVS, the Core OS team make a new branch *for every bug fixed* (my fault it's done that way). Each branch is merged down individually as the changes are approved by the group, and is allows engineers to hack away and commit as they go without disrupting anyone else. I'm talking about several hundred branches, and it's all running fine on some G4 box in a lab. On a smaller scale, but still bigger than the httpd-2.0 repository: At one place I do work we have almost 1 files in CVS where we frequently make several branches a week. It works fine. Sure, CVS branching isn't as nifty as what you have with perforce and probably subversion; but much nicer than duplicating the repository left and right. As Mark said, long-lived branches do take a hit, but that's why you branch off the maintenance release on leave active development on HEAD. The above mentioned project actually did it the other way around for the longest time. Not so nice, but I got them to change it because it's easier to manage with active development closer to HEAD, not because it was too slow otherwise. - ask -- ask bjoern hansen, http://www.askbjoernhansen.com/ !try; do();
Re: new download page
On Sat, 26 Oct 2002, David Burry wrote: [...] too... hmm.. This is probably getting to be too complex of a suggestion for anyone to do with volunteer time and resources but still just an idea... ;o) ftp'ing to ftp://ftp.perl.org/pub/CPAN/ generally sends you to a nearby CPAN mirror. ftp://ftp.apache.ddns.develooper.com/pub/apache/dist/ should find an Apache mirror not on the other side of the world. - ask -- ask bjoern hansen, http://www.askbjoernhansen.com/ !try; do();
Re: new download page
On Sat, 26 Oct 2002, Joshua Slive wrote: WHOIS parsing and stuff... _WAY_ overkilling... Anyhow this is going waaay offtopic! :-) See: http://maxmind.com/geoip/ If someone wants a little project, it shouldn't be too hard to integrate this into the existing closer.cgi script. FWIW, that's what my dynamic DNS thing I just mentioned is using. It translates the mirrors.dist file into a configuration file which is then used by the DNS servers. - ask -- ask bjoern hansen, http://www.askbjoernhansen.com/ !try; do();
RE: A suggested ROADMAP for working 2.1/2.2 forward?
On Thu, 17 Oct 2002, Bill Stoddard wrote:
* Consider using the Linux versioning system... stable release is 2.x where
x 0 and x == even. Developmemt release is 2.x where x is odd.
+100.
The Apache HTTPd versioning system has been plenty confusing to
people not following the httpd related ASF lists. Please make it
stop.
We did call Apache 2.0 stable, so the argument that 2.0 wasn't
stable so 2.{even} should be unstable seems pretty bogus to me.
--
ask bjoern hansen, http://www.askbjoernhansen.com/ !try; do();
Re: Concerns about suggested version strategy
On Fri, 18 Oct 2002, Justin Erenkrantz wrote: All even numbered releases will be considered stable revisions. [...] 1.99 series to do development for 2.0. (What is Perl doing for 6.0 development?) To answer your question first: For mod_perl we are using 1.99_[patchlevel] for the development releases leading to mod_perl 2.x. I don't think there are any plans for using the odd/even scheme for mod_perl. With Perl it's a bit different; Perl6 is an entire rewrite, so it doesn't really count. We only started using the odd numbers for development releases with perl 5.6; previously to that the versioning scheme was [major]_[minor]_[patch_level]. The last version of perl 5.5.x was called 5.005_03. Back then we used patch level 50+ for development releases; so perl 5.005_50 was the first development release leading to 5.6.0 (which would have been 5.006 in the old scheme. Of course major has not changed for 5 years (this Thursday IIRC!), so it got a bit silly; hence the change to using the major.minor.patch which really should be treated more like 5.major.minor. :-) Regardless of what Linux or Perl do, I think there is a real problem with having stable be even and odd be development. (We could treat zero as odd, but then we have 0, 1 as both odd - ick. So, zero is traditionally even in our context.) So, I'd much prefer that we stick with OtherBill's initial suggestion - it makes it easier for us to do development on new major numbers. The first odd release (0 != odd) is a stable release. It just makes more sense. I don't think it makes sense at all. Lots of software is unstable in the .0 release, but I never heard of it being that way intentionally. And we try to be better than the rest, no? :-) I'd also like to quantify what a major number bump means. My guess would be, Brand new architecture in httpd X. You have no hope of porting your X-1 modules. Don't even try. +1 to that. (of course with mod_perl we have a compatibility API, so most old modules will actually work :-) ) [...] Let's say someone did an auth rewrite and it lived for a long time in -development. I don't think there are any grounds for keeping it out of -stable. Everything in -development must be there with the knowledge that it should be included in the next -stable release. Yes! Otherwise it doesn't make any sense. - ask (bikeshedding away) -- ask bjoern hansen, http://www.askbjoernhansen.com/ !try; do();
RE: stable 2.0 trees
On Tue, 15 Oct 2002, Bill Stoddard wrote: Worth reading... http://techupdate.zdnet.com/techupdate/stories/main/0,14179,2882203,00.html On October 2nd; *after* RedHat 8.0 was released he wrote And I doubt Red Hat will make 2.0 the default install until [...]. Really Impressive Predictions. - ask -- ask bjoern hansen, http://www.askbjoernhansen.com/ !try; do();
Re: graceful?
On Mon, 23 Sep 2002 [EMAIL PROTECTED] wrote: Has anybody torture tested graceful restarts lately? I only ask because we just got a PR that gave me that sinking feeling. Maybe not a real problem, but just figured I'd ask. They work on daedalus with prefork. But that's typically just once a night - not sure if that qualifies as a torture test. It fails sometimes for me on Linux (pretty standard RedHat 7.3) with the worker MPM. (The original parent process (if that's what you call it) just hangs until you kill it). Actually, it might not have failed since sometime around .40; I haven't paid that much attention. I will try to look closer if it happens again. (how was that for a useless bug report? :-) ) - ask -- ask bjoern hansen, http://www.askbjoernhansen.com/ !try; do();
Re: Tagged the tree
On Sun, 8 Sep 2002, Greg Stein wrote: [...] Personally, I would just advocate shifting to Subversion. Part of our release process injects the revision number into the header file. Thus, the tarball always states *precisely* what revision the code came from. FWIW; for perl5 perforce is used in a similar fashion. Most people test tar balls (or whatever) named after the change number. People can then reference uhu, blah broke in 19583. Yes, I tried fixing foo. Can you try 19587 for me?. Works pretty well as far as I can see. - ask -- ask bjoern hansen, http://www.askbjoernhansen.com/ !try; do();
Re: Is it time to split the APR/HTTPD releases ?
On Sun, 8 Sep 2002, Aaron Bannert wrote: [sorry for the crosspost. I'm moving this branch of the conversation to the dev@apr list] Except of course that we have ezmlm munge the reply-to headers so you can't control such things... - ask (who couldn't resist, sorry) :-) -- ask bjoern hansen, http://www.askbjoernhansen.com/ !try; do();
Re: Releasing 2.0.41
On Fri, 6 Sep 2002, William A. Rowe, Jr. wrote: We consider Apache 2.0.x to be the best version of Apache available How about adding a box on http://httpd.apache.org/ that says something like 2.0.40 is our latest stable release There are no current beta releases available 2.0.41 is our latest alpha release maybe with a little explanation of the system below (that any alpha release might or might not be moved to stable or beta later). - ask -- ask bjoern hansen, http://www.askbjoernhansen.com/ !try; do();
Re: 2.1 repository?
On Fri, 30 Aug 2002, Justin Erenkrantz wrote: (leaving 2.0 as head, so nobody following older checkout instructions to grab the now-current version have a 'surprize' in store.) I tend to find myself agreeing with him on this. As Marc pointed out, that won't work with CVS. And, because I think it is very counter-intuitive if I check out httpd-2.0 and get 2.1 - something isn't right there. I'm sure you'll be able to grok that. Alternately the repository could be renamed to httpd-2 (as you almost suggested yourself). [...] Look at all of the repositories we created that are still left around: apache-1.2 apache-1.3 apache-apr apache-nspr httpd-2.0 The apache-apr and apache-nspr repositories were fairly short-lived. I wasn't around when they were created, so perhaps the intention really was that they would be the 'next big thing.' Not sure about apache-apr, but IIRC apache-nspr was a combination of next big thing and sandbox for trying out this fancy styff. - ask -- ask bjoern hansen, http://www.askbjoernhansen.com/ !try; do();
Re: mod_cache trouble
On Tue, 27 Aug 2002, Ask Bjoern Hansen wrote: Are you using the most recent head build of 2.0? There was a fix applied recently to the header handling for mod_disk_cache. I am currently doing some work on the caching code, so I'll look into this. Please let me know if you are on the latest code. FWIW; it mostly works for me now. I'm not entirely sure why it didn't before (and still doesn't for the nntp site in the previous example). I figure I'm lacking some understanding of how mod_cache is dealing with the headers. (Need to read through the code again). Btw, the Age: header inserted by mod_cache seems to be in microseconds or something like that (instead of seconds). - ask -- ask bjoern hansen, http://www.askbjoernhansen.com/ !try; do();
relative log file locations in 2.0.41-dev
It seems like the latest httpd from CVS doesn't prepend ServerRoot to to log paths. If I start the httpd like this, /home/perl/apache2/bin/httpd -d /home/web/front/ -k start -e debug I get an error that it can't open logs/error_log. If I chdir to /home/web/front/ I don't get an error message, but the httpd silently just exits. If I change the log paths to absolute paths everything works fine. - ask -- ask bjoern hansen, http://www.askbjoernhansen.com/ !try; do();
mod_cache trouble
I am using the latest httpd from CVS.
I can't get mod_disk_cache to cache anything but 301's.
I suspect it's something related to the headers I (don't) send.
$ lwp-request -e -d -S http://nntp.x.perl.org/
GET http://nntp.x.perl.org/ -- 200 OK
Connection: close
Date: Tue, 27 Aug 2002 11:34:58 GMT
Via: 1.0 nntp.x.perl.org
Server: Apache/1.3.26 (Unix) mod_perl/1.27
Content-Length: 1896
Content-Type: text/html; charset=ISO-8859-1
My httpd.conf looks like the following,
LoadModule cache_module modules/mod_cache.so
LoadModule disk_cache_module modules/mod_disk_cache.so
[...]
VirtualHost *
servername nntp.x.perl.org
serveralias nntp.perl.org
CacheOn on
CacheRoot /home/web/front/cache/
CacheSize 5
CacheDefaultExpire 43200
CacheEnable disk /
CacheDirLevels 5
CacheDirLength 3
RewriteEngine On
RewriteCond %{REQUEST_URI}!^/js/
RewriteCond %{REQUEST_URI}!^/proxy-status
RewriteRule (.*) http://localhost:8222$1 [P]
/VirtualHost
[...]
- ask
--
ask bjoern hansen, http://www.askbjoernhansen.com/ !try; do();
Re: daedalus is running 2.0.40 live
On Fri, 9 Aug 2002, Greg Ames wrote: portable way to do this. Maybe I should just hack apbounce to look for a listener on port 80 once a second or something. I usually make my restart the httpd script look for the pid, run apachectl stop and then wait until you can't kill(pid, 0) anymore before proceeding. - ask -- ask bjoern hansen, http://www.askbjoernhansen.com/ !try; do();
Re: 2.0 book
On Thu, 27 Jun 2002 [EMAIL PROTECTED] wrote: If not... what's the price tag for this book and will you allow portions of it to be reprinted online for users of this 'public domain' software? Apache is not public domain software. A quick lookup says that the list price is $49 and street price will be ~$35. http://www.allbookstores.com/book/compare/0072223448 - ask -- ask bjoern hansen, http://askbjoernhansen.com/ !try; do();
Re: Bugzilla action items
On Sun, 17 Mar 2002, Justin Erenkrantz wrote: 5) Potentially add a bugzilla.apache.org CNAME that is a redirect to http://nagoya.apache.org/bugzilla. [DNS and httpd admin] How about changing the bugzilla installation to be known as bugzilla.apache.org (so no redirect). -- ask bjoern hansen, http://ask.netcetera.dk/ !try; do();
Open Source Convention, Apache Httpd, Call for Participation (dueMarch 1st) (fwd)
Call for Participation - Proposals Due March 1, 2002 O'Reilly Associates is pleased to announce the 4th annual Open Source Convention. The Open Source Convention is a five-day event designed for programmers, developers, strategists, and technical staff involved in Open Source technology and its applications. This event is the central gathering place for the Open Source community to exchange ideas, share techniques, push the technical boundaries, and maximize the benefits of open source software. The convention takes place at the Sheraton San Diego Hotel and Marina, San Diego, California, July 22-26, 2002. The theme this year is Doing More With Less. This has several aspects: how business can do more with less money (by adopting open source software), how developers do more with less time and financial support, how to make the most of what you've got (performance tuning and little-known-of features), and how open source software manages to avoid the bloat that characterizes closed-source software. Suggestions for things that would be great to see in the Apache httpd track, * Apache 2.0's new features, why it took so long, and what the future holds * Strategies to get better performance (mod_backend, Squid, ...) * 5 coolest modules shipping with Apache that most people never use * Writing Apache 2.0 handlers * Success story about BigCorp, Inc using Apache and being proud of it (how we replaced umpteen NT boxes with a handful of Apache servers) * Security Individuals and companies interested in making presentations, giving a tutorial, or participating in panel discussions are invited to submit proposals. Proposals will be considered in two classes: tutorials and convention presentations (sessions). Presentations should be aimed at a 45- or 90-minute time slot, though full day and half day tutorials are another option. Presentations by marketing staff or with marketing focus will be rejected. All presenters whose talks are accepted will receive free registration at the conference. For each half-day tutorial, the presenter receives one night's accommodation, a travel allowance, and an honorarium. Registration will open April 1, 2002. If you would like an email notification when registration opens, please use the form on http://conferences.oreillynet.com/os2002/#notify For more information see http://conferences.oreillynet.com/cs/os2002/create/e_sess -- ask bjoern hansen, http://ask.netcetera.dk/ !try; do();
borken file permissions on daedalus (fwd)
-- 2nd Fwd message -- Subject: RE: Output from cron command Date: Fri, 14 Sep 2001 08:37:07 +1000 From: Andrew Kenna [EMAIL PROTECTED] To: 'Jose Manuel Macias Luna' [EMAIL PROTECTED] please forward these responses into [EMAIL PROTECTED] as if you email this list it only gets to 3 people, none of which can fix the errors you are getting. miror-submit is only for people who want to become an apache mirror, not someone who is having problems mirroring the apache server. Andrew Apache Mirror Team -Original Message- From: Jose Manuel Macias Luna [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 13, 2001 7:11 PM To: [EMAIL PROTECTED] Subject: Fwd: Output from cron command Hello, we are having problems to make our mirror of apache, below is the rsync log. I laso have to inform you that our apache mirror is available through: ftp://ftp.rediris.es/mirror/apache and also http://apache.rediris.es This is a thttpd server, not an Apache, but if you want to link it you are welcome. We use apache in many of our servers but we chose thttpd for our mirroring service. -- Original Fwd message -- Subject: Output from cron command Date: Thu, 13 Sep 2001 00:40:07 +0200 (CEST) [...] Your cron job on zeppo [...]/rsync.apache produced the following output: receiving file list ... done send_files failed to open dist/httpd/binaries/aix/old/apache_1.3.1-rs6000-ibm-aix3.2.README: Permission denied send_files failed to open dist/httpd/binaries/aix/old/apache_1.3.1-rs6000-ibm-aix3.2.tar.gz: Permission denied send_files failed to open dist/httpd/binaries/aix/old/apache_1.3.1-rs6000-ibm-aix3.2.tar.gz.md5: Permission denied send_files failed to open dist/httpd/binaries/aix/old/apache_1.3.12-002257794C00-ibm-aix4.2.README: Permission denied send_files failed to open dist/httpd/binaries/aix/old/apache_1.3.12-002257794C00-ibm-aix4.2.tar.gz: Permission denied send_files failed to open dist/httpd/binaries/aix/old/apache_1.3.12-002257794C00-ibm-aix4.2.tar_gz.asc : Permission denied send_files failed to open dist/httpd/binaries/aix/old/apache_1.3.6-rs6000-ibm-aix4.2.README: Permission denied send_files failed to open dist/httpd/binaries/aix/old/apache_1.3.6-rs6000-ibm-aix4.2.tar.gz: Permission denied send_files failed to open dist/httpd/binaries/aix/old/apache_1.3.9-002257794C00-ibm-aix4.2.README: Permission denied send_files failed to open dist/httpd/binaries/aix/old/apache_1.3.9-002257794C00-ibm-aix4.2.tar.gz: Permission denied send_files failed to open dist/httpd/binaries/aix/old/apache_1.3.9-002257794C00-ibm-aix4.2.tar_gz.asc: Permission denied send_files failed to open dist/httpd/binaries/aix/old/apache_1.3.9-0035558C4C00-ibm-aix4.3.README: Permission denied send_files failed to open dist/httpd/binaries/aix/old/apache_1.3.9-0035558C4C00-ibm-aix4.3.tar.gz: Permission denied send_files failed to open dist/httpd/binaries/aix/old/apache_1.3.9-0035558C4C00-ibm-aix4.3.tar_gz.asc: Permission denied mail/apache-bugdb/200109 mail/apache-docs/200109 mail/modproxy-dev/200109 mail/apache-bugdb/ mail/apache-docs/ mail/modproxy-dev/ wrote 6039 bytes read 62795 bytes 9177.87 bytes/sec total size is 532147829 speedup is 7730.89 --- Thanks in advance, José Manuel. -- Sistemas de Informacion - webmaster, ftpmaster Centro de Comunicaciones CSIC/RedIris Spanish Academic Network for Research and Development Madrid (Spain) Tlf 91.585.51.50
Re: zlib inclusion and mod_gz(ip) recap
On Wed, 5 Sep 2001 [EMAIL PROTECTED] wrote: In a message dated 01-09-05 14:44:54 EDT, Marc Selmko wrote... Why do you quote Ken's mails as coming from a Mr. Selmko? Who is he anyway? - ask -- ask bjoern hansen, http://ask.netcetera.dk/ !try; do(); more than a billion impressions per week, http://valueclick.com
