Re: board report due tomorrow
On 18.02.2008, at 21:09, Dirk-Willem van Gulik wrote: On Feb 18, 2008, at 7:57 PM, Roy T. Fielding wrote: On Feb 18, 2008, at 4:32 AM, Issac Goldstand wrote: Nick Kew wrote: On 18 Feb 2008, at 08:29, Issac Goldstand wrote: I think we also adopted mod_dns at Apachecon, That'll be *cough* _provisionally_ adopted. Decisions are made on-list. Remind me where to find the thread. I hope this link works, as I haven't used Markmail's new UI very much yet: http://httpd.markmail.org/search/?q=mod_dns#query:mod_dns+page:1 +mid:juhrpyxq635mhy6n+state:results Ah, the problem with having a proposal that lots of people +1 and nobody concludes with a "okay, it's approved, now here's what we do next" message I've started to dive into that - and am quite prepared to wack it into shape. However I've only found iCLA's and cCLA's sofar - and am waiting for Jonathan to let me know if there is a software grant for mod_dns itself. It's recorded in grants.txt for "Mod_dns" - though I couldn't find a scan for it. Cheers, Erik
Re: ping on mod_dns
On 18.02.2008, at 20:03, Roy T. Fielding wrote: On Feb 9, 2008, at 4:21 PM, Issac Goldstand wrote: Any volunteers to import mod_dns so I can eventually start hacking at it again (topic came up at work recently and I have a couple of feature ideas that I'd like to work on, but really don't want to have to work in my old svn + port changes to asf svn too)? AFAIK, we finished with the red tape already (please tell me off- list if I'm wrong) Actually, I'd rather do that on-list so that more people know what is required. We already had the proposal and enough +1 votes to add mod_dns as a subproject. http://markmail.org/message/juhrpyxq635mhy6n The next question is about the intellectual property. ... See also the thread 'Issac Goldstand / mod_dns' on board@ for some info re paper-work (02/10/2008)... Cheers, Erik
Re: DisableReuse for mod_proxy
On 13.02.2008, at 16:27, Jim Jagielski wrote: I added something similar to mod_jk quite awhile ago, and I'm trying to get mod_jk and mod_proxy closer to parity, esp for those using AJP. So with that in mind, comments on the below?? Index: docs/manual/mod/mod_proxy.xml === --- docs/manual/mod/mod_proxy.xml (revision 627440) +++ docs/manual/mod/mod_proxy.xml (working copy) @@ -693,6 +693,16 @@ in the pool the Apache will return SERVER_BUSY status to the client. +disablereuse +Off +This parameter should be used when you want to force mod_proxy +to immediately close a connection to the backend after being used, and +thus, disable its persistant connection and pool for that backend. "persistent" instead of "persistant"? +1 to the rest. Cheers, Erik
Re: What am I doing wrong - site gen?
On 24.01.2008, at 00:53, William A. Rowe, Jr. wrote: security/vulnerabilities-oval.xml I'm ending up with deltas such as these... -http://oval.mitre.org/XMLSchema/oval- definitions-5#apache" id="oval:org.apache.httpd:ste:131" version="1" comment="the version of httpd is 1.3.1"> -1.3.1 +http://oval.mitre.org/XMLSchema/oval- definitions-5" id="oval:org.apache.httpd:ste:131" version="1" comment="the version of httpd is 1.3.1"> +http://oval.mitre.org/XMLSchema/oval- definitions-5#apache" operation="equals" datatype="version">1.3.1version> What component are we missing in site/lib/ or should I have locally updated? I guess you were running Ant directly instead of via build.sh, right? If so then it was probably overriding the jars in site/lib and was therefore using a different version of the xslt processor... To get consistent results we need to rely on the jars in site/lib and only running via build.sh ensures that those are picked up :-/ Can you please try and let me know? I'll then update README if that fixes the issue... Oh, and if you can't run build.sh on Win* (e.g. no cygwin) then we'll need to add a .bat version for it... (for an example see docs-build/ trunk/build.bat). Cheers, Erik
Re: ping on mod_dns
On 10.02.2008, at 14:16, Dirk-Willem van Gulik wrote: On Feb 10, 2008, at 1:21 AM, Issac Goldstand wrote: Any volunteers to import mod_dns so I can eventually start hacking at it again (topic came up at work recently and I have a couple of feature ideas that I'd like to work on, but really don't want to have to work in my old svn + port changes to asf svn too)? I'd be quite interested to see this go in as 'experimental' or similar. Same here, I'd be interested in that as well - of course for now only as experimental. Cheers, Erik
Re: PATCH -- make the cache modules part of 'all'.
On 08.02.2008, at 23:57, Ruediger Pluem wrote: On 02/08/2008 07:58 PM, William A. Rowe, Jr. wrote: Jim Jagielski wrote: On Feb 8, 2008, at 12:01 PM, Nick Kew wrote: On Fri, 8 Feb 2008 16:07:40 +0100 Dirk-Willem van Gulik <[EMAIL PROTECTED]> wrote: Given that mod_cache is now quite mature - perhaps time to make it part of the 'all' setting in ./configure (and we could argue same for ssl and ldap). And hence make it part of the general body distributed by the vendors (who seem to follow our "all" config). That begs the question, what do we mean by "all"? It currently excludes proxy and dav, as well as the modules you mention. That's IMHO rather more confusing than it should be. +1 :) +1 - there's only two classes of exceptions IMHO - those would be SSL, and pure test modules. And I'm +/-0 on including those test modules in 'all' (but never in 'most'). My personal preference is that ANY production module, except for SSL, is automatically grabbed up with "all". So proxy and dav are mistakes IMHO. +1 to this, but keep the test modules out of 'all'. +1, please no debug/test modules in 'all'. Cheers, Erik
Re: [Fwd: website]
On 08.01.2008, at 17:52, Sander Temme wrote: On Jan 8, 2008, at 5:37 AM, [EMAIL PROTECTED] wrote: Not acked, maybe already forwarded. What the are we supposed to do with an e-mail written: Date: April 17, 2004 10:21:24 PM PDT ??! Chris has probably graduated a long time ago and moved back into his mom's basement. It's really annoying that no contact email is listed for apache.org or httpd.apache.org. However, my main complaint is that you don't list the date that news items are posted, which is of critical importance and it's absurd that it's impossible to find out from your site when a particular version of apache was released. Fwiw, the news items on httpd.a.o also have a date now (since around Sep/Oct of last year) so... Cheers, Erik
Re: As we contemplate what to fix, and how to roll out 2.4 and 3.0
On 02.10.2007, at 20:52, Paul Querna wrote: So, the first step is to cut out any illusion that new features are going into 1.3, with a statement like this: Starting in January 2008, only critical security issues will be fixed in Apache HTTP Server versions 1.3.x or 2.0.x. I honestly believe we will be somewhat responsible for fixing any major security issues in 1.3 and 2.0 for the next 5-10 years, unless Waka suddenly explodes and replaces http :-) Thoughts? I really like that, but as Bill showed nicely (I love the last paragraph!) I think we should couple that with some PR... Cheers, Erik
Re: Adding timestamp to apache releases?
On 01.10.2007, at 12:22, Erik Abele wrote: On 01.10.2007, at 09:58, William A. Rowe, Jr. wrote: ... I like the idea of adding a date to each news item, be it on httpd.a.o, or our www.apache.org. +1. +1, see attached patch which adds dates to the index and download pages (see changes to site.vsl which add a 2nd column to the relevant section headers as soon as a new date="" attribute is present). Please test and give your opinion, works for me on Safari and Firefox... Got a chance to test it on IE today, looks fine so I've added it at the moment. Cheers, Erik
Re: Adding timestamp to apache releases?
On 01.10.2007, at 09:58, William A. Rowe, Jr. wrote: Boyle Owen wrote: Might it be an idea for 2.2.7? You can also get it from here for now: http://projects.apache.org/projects/http_server.html or as a feed: http://projects.apache.org/feeds/rss/http_server.xml I like the idea of adding a date to each news item, be it on httpd.a.o, or our www.apache.org. +1. +1, see attached patch which adds dates to the index and download pages (see changes to site.vsl which add a 2nd column to the relevant section headers as soon as a new date="" attribute is present). Please test and give your opinion, works for me on Safari and Firefox... Cheers, Erik dates.patch Description: Binary data
Re: 2.2.7
On 28.09.2007, at 01:28, William A. Rowe, Jr. wrote: Erik Abele wrote: Sure, we all have to pay our bills but you're overlooking a difference: Nick just replied to an inquiry offering his (and others services); he doesn't advertise any revenue-generating site after every release etc. etc... ;-0 Nick's comment didn't even mention he does this exclusively, he pointed out that there are a number of devs or organizations who can provide such services, and was *probably* letting the user know that the scope of their troubles was not going to elicit them enough purely voulenteer help. Exactly! Again, Steffens contributions would be very welcomed *here* if this whole AL thing were just not that misleading - hey, with some effort he could e.g. help out constructively by building these binaries in a transparent and documented way *here* and we could even distribute them from apache.org/dist (plus mirrors) to help the win community even more! I want to be sure folks understand that the relabeling that Steffan and the AL team have already done went a long way to satisfying almost any of the project's possible concerns; the Feather is gone, disclaimers are posted. W.r.t. actually creating or distributing RC's, Colm's points went a long way to convince me they can be helpful --- that is if and only if the feedback gets back to where it might be useful to improving the s/w. Absolutely. Also note we only post binaries from committers; we can't/won't elicit or host them for add'l third parties. So for example, any committer is welcome to post updated sun .pkg's. But we wouldn't accept those from Sun. The origin of all of the files under http://www.apache.org/dist/httpd/ is from an Apache httpd project committer, each of whom is bound to a CLA (to resolve any possible IP/trust issues.) Yep, maybe my post was misleading; with "some effort" I actually meant "becoming a committer"... :) Cheers, Erik
Re: 2.2.7
On 27.09.2007, at 17:04, François wrote: 2007/9/27, Erik Abele < [EMAIL PROTECTED]>: > Again, Steffens contributions would be very welcomed *here* if this > whole AL thing were just not that misleading - hey, with some effort > he could e.g. help out constructively by building these binaries in a > transparent and documented way *here* and we could even distribute > them from apache.org/dist (plus mirrors) to help the win community > even more! Then, create a svn access to apache lounge people that patch httpd As Jim and Ruediger already pointed out, that's not how the ASF works. You'll have to earn the merit - it's a trust thing ;) and stop to flame/troll/point at these guys. Oh, there's no flaming involved AFAICS; don't confuse constructive criticism with unsubstantial insults... but you're right, we should probably simply ignore it, don't feed the trolls etc... Cheers, Erik
Re: 2.2.7
On 27.09.2007, at 10:05, François wrote: 2007/9/27, William A. Rowe, Jr. <[EMAIL PROTECTED]>: [...] Here at [EMAIL PROTECTED] we are trying to create a better server, and having fun in the process. As long as we don't splinter the effort of improving httpd server or make more work for the project members, we'll all have fun at it. I'm not picking on you, let's solve the issues. Bill ... And the "we, for fun against you, for profit" argument is well demonstrated by a more recent mail of Nick Kew: "Some apache developers, including myself[1], make a living doing contract work for companies with development needs, such as yours. If you have a budget, I'll be happy to talk to you. The fact you're looking to make it available as open source will qualify you for a reduction in my standard rate." (And you talk about spam regarding apachelounge, please...) Thus, Apache commiters or developers are developping for fun (sometimes for fame) AND profit. ... Sure, we all have to pay our bills but you're overlooking a difference: Nick just replied to an inquiry offering his (and others services); he doesn't advertise any revenue-generating site after every release etc. etc... ;-0 Again, Steffens contributions would be very welcomed *here* if this whole AL thing were just not that misleading - hey, with some effort he could e.g. help out constructively by building these binaries in a transparent and documented way *here* and we could even distribute them from apache.org/dist (plus mirrors) to help the win community even more! Just my 2c... Cheers, Erik
Re: An enterprise-ish request (ie, basically SNMP)
On 13.09.2007, at 18:27, Jim Jagielski wrote: On Sep 13, 2007, at 12:11 PM, Erik Abele wrote: On 11.09.2007, at 19:26, Jim Jagielski wrote: ... I actually work for a company which is currently working out the logistics of open sourcing and donating our SNMP module. It would serve as a nice base to start from. Nice! I'd be happy to involve myself here too and provide patches, docs and also test the stuff; don't have the time (or interest) to start something from scratch though... Our pref, of course, would be to follow what we did with mod_ftp and donate it to the ASF and the httpd project. Sure, makes sense to follow that example and start in the Incubator; happy to give my +1 then and join the PPMC etc... We're in the process of cleaning up all the legal aspects and some code cleanups before we ping the PMC about it... ;) Cool :) Cheers, Erik
Re: An enterprise-ish request (ie, basically SNMP)
On 11.09.2007, at 19:26, Jim Jagielski wrote: On Sep 11, 2007, at 1:11 PM, Jeff McAdams wrote: For the benefit of the list...if there are other developers, in addition to Nick, that might be interested in taking a look at this project and tackling it, let me know and we can certainly talk. I actually work for a company which is currently working out the logistics of open sourcing and donating our SNMP module. It would serve as a nice base to start from. Nice! I'd be happy to involve myself here too and provide patches, docs and also test the stuff; don't have the time (or interest) to start something from scratch though... Cheers, Erik
Re: [VOTE] Apache 2.2.6, 2.0.61 and 1.3.39 release candidate tarballs for review
On 04.09.2007, at 23:29, Jim Jagielski wrote: Available for your testing pleasure, 3, count 'em, 3 Apache HTTP Server release candidate tarballs, located, as expected at: http://httpd.apache.org/dev/dist/ This vote will run through Sept 6, 2007 and close Sept 7, unless otherwise noted... +/-1 (x == +1) [ ]apache_1.3.39 Well, probably not a real blocker but the tarball (and therefore all compressed archives: Z, bz2, gz) for 1.3.39 expands to "apache-1.3" instead of "apache_1.3.39" as the name might suggest - this didn't happen for any other release yet and might overwrite something else (which just happened for me). Also the NOTICE file in there still says 2006 :( Cheers, Erik
Re: svn commit: r571928 - /httpd/httpd/branches/2.2.x/STATUS
On 02.09.2007, at 17:06, Tim Bray wrote: On Sep 2, 2007, at 5:24 AM, Graham Leggett wrote: [EMAIL PROTECTED] wrote: Is valid in XML? The answer is complicated. One approach is to use which is kinda ugly but works in lots more places. -T Yep, quite complicated - it has to do with Mozilla not loading external entities, etc. It's a long-known bug (since ~2000, see bugs #22942, #69799, #255747 and several others in Mozilla's Bugzilla); there are several work-arounds like using only internal entity defs, using and co or even populating Mozilla's /res/dtd directory but not one of them is really practical so we decided to just live with it... :( Cheers, Erik
Re: Guess what? Time for 1.3.39, 2.0.61 and 2.2.6 :)
On 01.09.2007, at 13:55, Nick Kew wrote: On Sat, 1 Sep 2007 00:53:16 +0200 Erik Abele <[EMAIL PROTECTED]> wrote: And can someone please also update the NOTICE file to carry the new copyright date? We are near to the end of 2007 and the file still says 2006; seems it wasn't touched since we changed all the license headers in July of last year ;-) Talking of which, a grep finds some more instances of 2006. Some interesting instances are ap_release.h Ohh, yah, good catch! and common.xsl from whence it propagates to every page of documentation! Re common.xsl please see the recent discussion on [EMAIL PROTECTED] Cheers, Erik
Re: Guess what? Time for 1.3.39, 2.0.61 and 2.2.6 :)
On 30.08.2007, at 15:02, Jim Jagielski wrote: Yes, the CHANGES file will be updated to reflect any and all security issues for that release... And can someone please also update the NOTICE file to carry the new copyright date? We are near to the end of 2007 and the file still says 2006; seems it wasn't touched since we changed all the license headers in July of last year ;-) Cheers, Erik
Re: Bug report for Apache httpd-2 [2007/07/01]
On 03.07.2007, at 01:44, Guenter Knauf wrote: Hi Erik, http://people.apache.org/~erikabele/httpd/bugstats/ looks very great; but seems that only the 1.3.x stats are uptodate - the 2.x stats unfortunately stop at 2005/11/27 ... Ooops, right, something seems to be broken, will have a look. for some more motivation :-) hmm, but one person alone cant do anything; if someone picks up a bug and tries to solve it some feedback of others is required... Sure, didn't imply anything :) so we would need some common agreement that we make a bugfix round and concentrate on that for a while; and if one asks for feedback on a solution that feedback is given until there's a solution to the issue. Yep though that's not always possible with volunteer-based development; anyway, I'd assume that if one person starts to give some bugs some more visibility e.g. by posting them to the dev list, then the comments will come... otoh there are quite some people very active on bugzilla so it's not that nothing is happening over there :) BTW. the monthly bug reports are not online somewhere available, or? They're in the mailing list archives, but not published separately afaik. How do you collect the data? No magic involved, see http://people.apache.org/~erikabele/httpd/ bugstats/genstats Cheers, Erik
Re: Bug report for Apache httpd-2 [2007/07/01]
On 02.07.2007, at 22:48, Guenter Knauf wrote: probably it helps a little bit to reduce these 888 bugs if we can easier read... http://www.gknw.net/apbugs/ http://www.gknw.net/apbugs/?version=13 Or see http://people.apache.org/~erikabele/httpd/bugstats/ for some more motivation :-) Cheers, Erik
Re: [Vote] create [EMAIL PROTECTED]
On 01.09.2006, at 21:25, William A. Rowe, Jr. wrote: Project Committee Members... Adopt [EMAIL PROTECTED], seeded from apache- [EMAIL PROTECTED] current subscribers, for module authors to use for peer developer support? (API 'users', essentially.) [X] +1 [ ] +/-0 [ ] -1 With a -1 on automatically moving subscribers - either please send clear instructions on how to move oneself or perhaps, as Nick suggested, make it an opt-out process with at least two reminders (though that might be harder to manage/track/... and not really worth it?). Cheers, Erik smime.p7s Description: S/MIME cryptographic signature
Re: doap file
On 23.01.2006, at 23:13, David Reid wrote: Erik Abele wrote: Since this is not trunk-specific and doesn't really belong to the source and/or release of a specific version, I'd prefer to keep this file somewhere in [1] instead of [2]... that may sound a bit picky but it's a bit cleaner IMHO (accessible via HTTP w/o SVN backend, repo permissions: docs people can access /site/trunk which might not be always true for httpd/trunk, 'nicer' URL for outside usage, etc.)... Comments? The only reason for keeping it under trunk was that having it there it's available to people doing releases. Putting it under site means that those wishing to do a thorough review means they have to have 2 repos checked out. *shrug* Yep, they will need it anyways for the site changes (download.xml, index.xml) and furthermore you need a third checkout for the announcement: http://svn.apache.org/repos/asf/httpd/httpd/dist/ ;-) I don't really care and so will move it. Already done, I just moved it over to http://httpd.apache.org/ doap.rdf while I finally removed the AC05 blurbs :) Cheers, Erik smime.p7s Description: S/MIME cryptographic signature
Re: doap file
[CC'ing docs to also let them know that there's something to maintain ;-)] On 23.01.2006, at 10:43, David Reid wrote: I've committed a DOAP file into the trunk repo. This file is referenced by http://projects.apache.org and so we should be keeping it up to date. That site also has details on what it all means and the data that it should contain. Since this is not trunk-specific and doesn't really belong to the source and/or release of a specific version, I'd prefer to keep this file somewhere in [1] instead of [2]... that may sound a bit picky but it's a bit cleaner IMHO (accessible via HTTP w/o SVN backend, repo permissions: docs people can access /site/trunk which might not be always true for httpd/trunk, 'nicer' URL for outside usage, etc.)... Comments? Cheers, Erik [1] http://svn.apache.org/repos/asf/httpd/site/trunk/docs/ [2] http://svn.apache.org/repos/asf/httpd/httpd/trunk/ smime.p7s Description: S/MIME cryptographic signature
Re: mod_mbox 0.2 goes alpha
On 20.12.2005, at 23:45, William A. Rowe, Jr. wrote: Maxime Petazzoni wrote: I was going to do that when I was told on #httpd-dev that it was easier to drop it in my people.apache.org web space : 16:45:08 colmmacc | well, that gets mirrored, I'd use people.apache.org/~whatever/ 16:45:17 colmmacc | that's what the cool kids have used lately ;-) httpd.apache.org/dev/dist/ is mirrored? Even if it is, just don't worry about that. Our convention is that anything in dev/dist/ is nothing but a candidate, not a proper release. Just for the record: no, httpd.apache.org/dev/dist (minotaur:/www/ www.apache.org/dev/dist) is not mirrored - only www.apache.org/dist (minotaur:/www/www.apache.org/dist) is mirrored. Cheers, Erik smime.p7s Description: S/MIME cryptographic signature
Re: 321greetings' Auto Responder
FYI: I just unsubscribed this address from [EMAIL PROTECTED] Cheers, Erik Am 04.05.2005 um 10:30 schrieb [EMAIL PROTECTED]: Hi, Due to the amount of e-mails we get per day we have setup this auto responder for your convenience. This is not a monitored e-mail address To unsubscribe http://321greetings.com/unsubscribenewlist.htm http://321greetings.com/unsubscribenewlist.htm \\\"> AOL Link To subscribe please go here: http://321greetings.com/sub321greetings-newsletter.htm http://321greetings.com/sub321greetings-newsletter.htm \\\"> AOL Link If you need technical assistance, please go here: http://321greetings.com/contactus.htm http://321greetings.com/contactus.htm \\\"> AOL-link smime.p7s Description: S/MIME cryptographic signature
Re: RFC: UserDir off by default for 2.1/2.2
On 31.03.2005, at 18:54, Roy T. Fielding wrote: IMO, it should be off by default on all httpd versions, just as the config should default to no access. Personally, I would prefer that all of the defaults be set internal to the server such that a running httpd with an empty status file would only I presume you meant *config* instead of *status* file? be capable of responding successfully to "/" with a simple "You need to configure the server now." Everything else should be a 403 or 404 until it is explicitly configured. Not that I'd volunteer to implement that but I really like the approach. +1 on patch. Same here, +1. Cheers, Erik smime.p7s Description: S/MIME cryptographic signature
Re: Forthcoming 2.2 - Win32 specific questions
On 29.03.2005, at 23:42, William A. Rowe, Jr. wrote: 'Apache' was our program. It became our project. It's become our entire organization. In 2.2, I -will- be changing the default location for the Win32 installer from %programsdir%\Apache Group\Apache2\ over to %programsdir%\Apache Software Foundation\Apache HTTP Server 2.2\. This is consistent with the Tomcat group's installer changes. They actually considered taking a step backwards and changing their installer from 'Software Foundation' to 'Group'. I assured them we will be changing to better reflect today's organization. As the unix binary is 'httpd', it seems time to change the Win32 binary to 'httpd.exe'. It just seems to be a bit archaic to continue to use 'Apache.exe' when you look at www.apache.org and consider what the foundation's become. So can I have a quick vote before beta to rename our program to 'httpd.exe' on Windows, matching our Unix builds? +1 on both renames. Cheers, Erik smime.p7s Description: S/MIME cryptographic signature
Re: Puzzling News
On 01.03.2005, at 15:18, Graham Leggett wrote: Paul A Houle said: I think of all the features that web site authors and developers need that still don't exist in mainstream web servers; part of this is in the area of "content management" and another major are is authentication -- pretty much any serious interactive web site needs a cookie-based authentication system with the features seen on big sites like amazon.com and yahoo! and one of the reasons there is so little code reuse on the web is that every application winds up impementing it's own authentication system; if there was something really good built into a market-leading web server, this picture would change completely. The trouble with the authentication problem is that the credentials used for authentication are often used for way more than just finding out whether a user has access. That said, this is definitely a very useful addition. Something like an auth module that can do "form based" auth, in addition to "basic" and "digest" etc would probably be very useful. Looks like someone is working on that: http://csce.uark.edu/~ajarthu/mod_auth_form/ Cheers, Erik smime.p7s Description: S/MIME cryptographic signature
Re: Authentication Needs for Apache: Was Re: Puzzling News
On 01.03.2005, at 15:52, Sean Mehan wrote: Just a pointer to something that is gaining a bit of ground in various circles: http://www.oasis-open.org/committees/download.php/11511/sstc-saml- tech-overview-2.0-draft-03.pdf found at http://www.oasis-open.org/committees/documents.php?wg_abbrev=security This is about SAML, a vocabulary for exchange of authentication and authorization data about users trying to access resources. With this capability built in, one can write policies for users originating from other sites. The problem I see with SAML and it's specs is that RSA holds patents on it and although these patens are made available under a royalty-free license, every end-user must obtain their own licsense from RSA. That alone is a requirement which goes far beyond the requirements of the Apache License and furthermore there are some other constraints (e.g. licensees must grant RSA the same rights to any patents they own). Find the details at http://www.oasis-open.org/committees/security/ipr.php. There is an implementation of this for what used to be called (resource) targets, now called SP [service provider]s, which compiles and runs under apache 1.3/2.0 found at http://shibboleth.internet2.edu/ Hmm, I think both, opensaml.org and shibboleth.internet2.edu are not conforming to RSA's license requirements: "The license terms for the RSA Patents will permit end-users to use the Licensed Products. However, in the event that a Licensed Product is a product (such as a toolkit product or operating system service) that is used to develop other products, the license will require the licensee of the RSA Patents to notify users of the Licensed Products that such users must obtain a license directly from RSA for the RSA Patents. RSA is willing to grant such licenses on the same non-exclusive, royalty-free terms described above." I don't find any such notice on both pages, just their usual license which is misleading in this case, e.g. http://www.opensaml.org/license.html IMHO we should avoid touching this sort of stuff... Cheers, Erik smime.p7s Description: S/MIME cryptographic signature
Re: svn commit: r124599 - /httpd/httpd/trunk/modules/config5.m4
On 25.01.2005, at 15:21, Joe Orton wrote: On Tue, Jan 25, 2005 at 02:09:06PM +0100, Erik Abele wrote: Exactly, this just keeps --with-module consistent with the rest of the build system, in respect to the changes introduced by Joe. (Sorry, Bill, I somehow missed your original mail...) Actually it doesn't, there was a subsequent change to use "libmod_*.la" for statically-linked modules, since creating a "libfoo.la" which is linked against a "-lfoo" confuses libtool. Correct, I somehow missed r103164: - libname="lib$1.la" + libname="libmod_$1.la" Will fix this ASAP... On 2.0 statically-linked modules still use filenames like "mod_*.la", so it's not consistent with that either ;) Also correct and of course doesn't make sense without your changes. Will remove the backport vote. I wasn't sure: what motivated your change, just consistency? My changes were made to fix issues using as-yet-unreleased versions of libtool. While extending --with-module I experienced problems like 'The filename of a convenience library must have a "lib" prefix' when building modules on OS X with libtool-1.5.10, the solution was obviously the change from r102381... Cheers, Erik smime.p7s Description: S/MIME cryptographic signature
Re: svn commit: r124599 - /httpd/httpd/trunk/modules/config5.m4
On 23.01.2005, at 18:43, Justin Erenkrantz wrote: On Mon, Jan 10, 2005 at 01:11:34AM -0600, William A. Rowe, Jr. wrote: Please describe what this actually does? Are we back to libproxy.la, libssl.la after this change? For static modules, yes. This was modified in r102381 by Joe: --- Correct use of libtool: libtool convenience libraries which are to be linked directly into a program must be linked using -static and not -module. Fixes build issues with libtool HEAD. --- Erik's change just catches up the manual modules to this change. -- justin Exactly, this just keeps --with-module consistent with the rest of the build system, in respect to the changes introduced by Joe. (Sorry, Bill, I somehow missed your original mail...) Cheers, Erik smime.p7s Description: S/MIME cryptographic signature
Re: Proposal: R-T-C and packaging files
William A. Rowe, Jr. said: For a stable branch though - more often such changes should just be -vetoed- instead of worked-around. Packaging changes would seem to signal breakage, not a reason for a workaround. -1 not CTR. Lazy consensus. Propose, give 3 - 5 days (what ever your schedule best provides) and then commit. If folks object they will speak up - if not - then you aren't hampered. just my 2 cent: -0 on CTR for the stable branch, +1 on lazy consensus (for packaging changes). Cheers, Erik smime.p7s Description: S/MIME cryptographic signature
Re: Is there a limit to using "with-module" directive ???
On 19.10.2004, at 04:03, Bennett, Tony - CNF wrote: I have tried "adding" two different home-grown modules to be statically linked when attempting to configure httpd 2.0.52 on AIX 5.1. My configure command: ... It only builds the module specified in the last "--with-module" directive. Is this a limitation with that directive ??? If so, how do I "add" two modules that are to be statically linked…? This should be working now with the current SVN trunk (2.1.x), see http://cvs.apache.org/viewcvs.cgi?root=Apache-SVN&rev=124600&view=rev Just use --with-module=module-type1:module-file1,module-type2:module-file2 to add two or more external modules - you can find a description at http://httpd.apache.org/docs-2.1/programs/configure.html - would be nice to hear the results... Cheers, Erik smime.p7s Description: S/MIME cryptographic signature
Re: moving docs build tools to httpd
On 24.11.2004, at 18:28, André Malo wrote: * Yoshiki Hayashi <[EMAIL PROTECTED]> wrote: After conversion is done, sending out instruction of how to update existing checkout would be nice. I believe you can just "svn switch" to the new location but I'm not sure. yep. just `svn switch new-url Did you already mv them, nd? I couldn't find it right now but maybe I'm just too blind with all the new stuff. In any case +1 on mv'ing /infrastructure/site-tools/trunk/httpd-docs-build/ to /httpd/docs-build/trunk Cheers, Erik smime.p7s Description: S/MIME cryptographic signature
Re: Bye bye welcome page
On 06.10.2004, at 18:07, Cliff Woolley wrote: On Wed, 6 Oct 2004, [ISO-8859-15] André Malo wrote: - there are 1000 people with 1000 other opinions. For that reason, I'm ++1 for taking this minimalistic variant. Otherwise we get never a consensus about this darn dummy page. That's an exceedingly good point. Make it so. :) +1. Same here, +1 - although... ;) Cheers, Erik smime.p7s Description: S/MIME cryptographic signature
FYI: bug statistics httpd-1.3/httpd-2.0
I'm building some simple (but nice) statistics based on the weekly bug reports mailed out to the dev- and bug-list: http://www.apache.org/~erikabele/httpd/bugstats/ The stats are updated every sunday just after the reports are mailed out. The script which produces the PNGs is also available at the above URL. Cheers, Erik ... in the hope of prodding some bug hunters ;) smime.p7s Description: S/MIME cryptographic signature
Re: [PROPOSAL] Move httpd to the subversion repository
On 13.03.2004, at 14:04, Sander Striker wrote: Hi, I hereby would like to propose that we move the HTTP Server project codebase to the Subversion repository at: http://svn.apache.org/repos/asf/. +1. I've proposed the same on the [EMAIL PROTECTED] list with respect to the APR project. It would be convenient, although not nessecary, if both projects decided to move at the same time. +1. Cheers, Erik smime.p7s Description: S/MIME cryptographic signature
Re: page out of date
On 26.01.2004, at 18:32, Aryeh Katz wrote: http://apache.get-software.com/httpd/binaries/win32/README.html doesn't have the correct version numbers. Fixed (also in HEADER.html). As an aside, would it make more sense to use SSI, and get the version number from the SERVER_SOFTWARE environment variable (I assume apache.org will always be running the most up to date version of apache). Perhaps on apache.org this would be doable but keep in mind that we don't have any control over the mirrors (see your URL above!). Furthermore there's usually only one version of Apache running, 1.3 or 2.0, so how would we get to the other version number? Cheers, Erik -- Aryeh Katz SecureD Services http://www.secured-services.com/ 410 653 0700 x 2 smime.p7s Description: S/MIME cryptographic signature
Re: Re-assigning bugs, was Re: DO NOT REPLY [Bug 26149]...
On 16.01.2004, at 10:30, Joe Orton wrote: On Fri, Jan 16, 2004 at 12:45:01AM +0100, Erik Abele wrote: Is it really enough to change the component to re-assign a bug to another project? Shouldn't the 'Assigned To:' field be filled with the appropriate mailing list address? Yeah, you have to remember to select the "Reassign bug to owner of selected component" option when changing the component. Ha, I knew there was something... thanks, Joe. Cheers, Erik /me goes to look how much mis-owned bugs are in bugzilla ;)
Re-assigning bugs, was Re: DO NOT REPLY [Bug 26149]...
On 15.01.2004, at 09:54, [EMAIL PROTECTED] wrote: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26149 Apache 2.0.48 won't load Tomcat 4.1.29 in-process via JK2 --- Additional Comments From [EMAIL PROTECTED] 2004-01-15 08:54 --- Changing to tomcat Is it really enough to change the component to re-assign a bug to another project? Shouldn't the 'Assigned To:' field be filled with the appropriate mailing list address? Not sure, but I realized that this bug is still assigned to [EMAIL PROTECTED] and didn't show up on tomcat-dev@ (http://mail-archives.apache.org/eyebrowse/BrowseList? listId=46&count=67297). Hmm... Cheers, Erik
Re: apache bug archive?
Have a look at the old gnats bug-archive (ranging back to '96): http://archive.apache.org/gnats/ Cheers, Erik On 15.01.2004, at 02:09, Min Xu(Hsu) wrote: Hi all, I wonder where can I find apache bug archive that goes further back than the bugzilla database? I am interested in searching through the bug database and picking out those data race related bugs. It seems that recent apache codebase is relatively bugfree with respect to these kind of bugs. Does any one remember what versions of apache had these kind of bugs? Maybe I can look through the changelog if I know what versions to look. Thanks a lot in advance! -Min -- Help them: http://www.ocef.org/newocef/en/
Re: check_forensic not working with GNU xargs?
On 13.01.2004, at 22:08, Ivan Ristic wrote: Checked on RH, Suse and Cygwin, all running the GNU version of xargs. On which platforms does it work? Works for me on FreeBSD and OS X and would work with -i on RH8.0's GNU version of xargs. Cheers, Erik
Re: cvs commit: httpd-2.0/docs/error README
On 06.01.2004, at 11:40, André Malo wrote: * [EMAIL PROTECTED] wrote: Changes with Apache 2.0.49 + *) Add Polish translation of error messages. PR 25101. + [Tomasz Kepczynski ] + iirc these made it never into the change log. The Swedish and the Polish ones did, e.g.: Revision 1.1347 - Thu Dec 18 15:29:41 2003 UTC (2 weeks, 4 days ago) by trawick http://cvs.apache.org/viewcvs.cgi/httpd-2.0/CHANGES?r1=1.1346&r2=1.1347 However, I think from a user POV the change warrants an entry in CHANGES, hmm... Cheers, Erik nd
Re: cvs commit: httpd-2.0/support/win32 ApacheMonitor.c ApacheMonitor.h ApacheMonitor.rc wintty.c
On 02.01.2004, at 14:34, Sander Striker wrote: On Fri, 2004-01-02 at 13:32, Ben Laurie wrote: [EMAIL PROTECTED] wrote: nd 2004/01/01 05:26:26 Log: update license to 2004. Why? Unless the file changes in 2004, the copyright doesn't. And, in any case, the earliest date applies, so it gets us nowhere. We seem to have this discussion every year. I'm too lazy to extensively dig in the archives, but: http://nagoya.apache.org/eyebrowse/ReadMsg? [EMAIL PROTECTED]&msgNo=79209 Roy: "That would change a lot more, and a lot less, than we want. I've committed the change for 2.0 and will do 1.3 next." Roy, care to explain what it is we want (and more importantly why)? I promise to mold the answer into a developer FAQ. IANAL (nor am I Roy, of course) but after reading http://www.copyright.gov/circs/circ1.html (especially #noc and #hlc) it appears to me that basically the correct way is what Ben suggested (only bump year when file changes): "The notice for visually perceptible copies should contain all the following three elements: ... 2. The year of first publication of the work. In the case of compilations or derivative works incorporating previously published material, the year date of first publication of the compilation or derivative work is sufficient. ..." On the other hand I don't see any harm in doing the bump in all files in one go since one can argue that in the end it's a combined work of all the files and we're just stating this in every, single file. So, when one file changes, the combined work changes and we've to change every file to reflect this fact. Does this make sense? just my 2c... Cheers, Erik
Re: the wheel of httpd-dev life is surely slowing down, solutions please
On 13.11.2003, at 02:10, Aaron Bannert wrote: On Thu, Nov 13, 2003 at 02:04:31AM +0100, Erik Abele wrote: I'd be very in favour of exploring other forms of bug-tracking. For example we'll have a full replication of BugZilla in Jira (/me hides) in the near future here on ASF hardware (see http://nagoya.apache.org/jira/ for a preview). I've to admit that I really like it and especially as a patch-tracking tool it could be useful, at least IMHO. Btw, Scarab (http://nagoya.apache.org/scarab/issues) is also available but I doubt that it is used by a single project ;-) My main requirement is that the bug tracking system be fully-accessible through email. Having a full web interface is great, but not at the expense of usable offline replies to bug reports. Okay, I can understand that. (Do either of these bug tracking systems support this?) Hmm, don't know, but I don't think so... Is bugzilla able to be fully controlled through email? Cheers, Erik -aaron
Re: the wheel of httpd-dev life is surely slowing down, solutions please
On 13.11.2003, at 01:29, Aaron Bannert wrote: On Mon, Nov 10, 2003 at 05:14:35PM -0800, Stas Bekman wrote: == 1) Bugs searching for NEW and REOPENED bugs in httpd-2.0 returns: 420 entries http://nagoya.apache.org/bugzilla/buglist.cgi? bug_status=NEW&bug_status=REOPENED&product=Apache+httpd-2.0 Suggestion: make bugzilla CC bug-reports to the dev list. Most developers won't just go and check the bugs database to see if there is something to fix, both because they don't have time and because there are too many things to fix. Posting the reports to the list raises a chance for the developer to have a free minute and may be to resolve the bug immediately or close it. Would anyone else be in favor of exploring other forms of bug-tracking? The old system (gnats) was completely email-oriented, which was good and bad. Bugzilla may be more usable for web-oriented users, but it it definitely more difficult to use offline (ie. impossible). Perhaps we could try out the bug tracking system used by the debian project (http://www.debian.org/Bugs/). I'd be very in favour of exploring other forms of bug-tracking. For example we'll have a full replication of BugZilla in Jira (/me hides) in the near future here on ASF hardware (see http://nagoya.apache.org/jira/ for a preview). I've to admit that I really like it and especially as a patch-tracking tool it could be useful, at least IMHO. Btw, Scarab (http://nagoya.apache.org/scarab/issues) is also available but I doubt that it is used by a single project ;-) Cheers, Erik
Re: UseCanonicalName semi-broken in 1.3.x
On 12.11.2003, at 18:15, Jim Jagielski wrote: It's been brought to my attention that UseCanonicalName in 1.3 is semi-broken, not completely honoring the port value when UseCanonicalName Off (see ap_get_server_port()). Heartburn if I fix this? dunno if you are already aware of this report: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24442 ...so just as a pointer, but generally +1 to a fix. Cheers, Erik
Re: htdocs in 1.3 CVS tree?
I'm able to reproduce the described symptoms every time I check out the apache-1.3 repo. I've looked into it now but couldn't find any problems so far. It'd be great if one of the CVS gurus (infrastructure is cc'ed) could have a quick look at this. Further info: a fresh checkout of httpd-docs-1.3 works fine. also an update of apache-1.3 which was checked out around mid-september (interestingly this tree is lacking the cgi-src and htdocs directory but both directories are visible in viewcvs?!?). Cheers, Erik On 04.11.2003, at 20:04, Geoffrey Young wrote: hi again I'm still seeing this error on my local system. since those who tried were not able to reproduce, I decided to try on cvs.apache.org > hostname minotaur.apache.org > mkdir src > cd src > cvs -z9 -d":pserver:[EMAIL PROTECTED]:/home/cvspublic" checkout apache-1.3 cvs server: Updating apache-1.3 ... U apache-1.3/src/test/vhtest/logs/.cvsignore cvs server: existing repository /home/cvspublic/apache-1.3/htdocs does not match /home/cvspublic/httpd-docs-1.3/htdocs cvs server: ignoring module htdocs-1.3 > ll apache-1.3/htdocs/manual/mod total 2 drwxr-xr-x 2 geoff geoff 512 Nov 4 10:57 CVS sorry if I seem like a nag, but it just doesn't seem right... --Geoff Geoffrey Young wrote: hi all when I do a fresh checkout of apache-1.3 $ cvs -z9 -d":pserver:[EMAIL PROTECTED]:/home/cvspublic" checkout apache-1.3 I see this error cvs server: existing repository /home/cvspublic/apache-1.3/htdocs does not match /home/cvspublic/httpd-docs-1.3/htdocs and htdocs is free of content. from modules, it looks like apache-1.3 should be both apache-1.3 apache-1.3 &htdocs-1.3 so I should be getting the docs too. is something amuck? it's been a while since I've looked at 1.3 cvs... --Geoff
Re: 2.0.48 tarballs ready for testing
On 26/10/2003, at 03:26, Sander Striker wrote: The tarballs for 2.0.48 are ready for testing. You can find them at: http://httpd.apache.org/dev/dist/ Looks good for me on OS X and RH Linux 9.0. +1 on both (2.0.48 & 1.3.29) tarballs. Cheers, Erik
Re: 1.3.29 tarballs available for testing, Take II
On 26/10/2003, at 02:46, Jim Jagielski wrote: If you've rec'd 2 copies of this (the 1st on Friday), please ignore. The 1.3.29 tarballs are available for testing at: http://httpd.apache.org/dev/dist Feedback desired and welcomed. Looks good for me on OS X and RH Linux 9.0. +1 on both (2.0.48 & 1.3.29) tarballs. Cheers, Erik
Re: ap_process_config_tree called twice -- causes command_rec entries to be called twice -- httpd-2.0.47
On 12/10/2003, at 09:33, John Millaway wrote: Hi, In httpd-2.0.47, command_rec entries are being called twice, via ap_process_config_tree. The first call occurs at main.c:581, and the second call occurs at main.c:638. The result is that the callbacks in a module's command_rec are called twice, as if the module's directives had appeared twice in the httpd.conf file. Is this supposed to happen? -John Yes, this is the intended behaviour, there's even a comment at main.c:564 /* Note that we preflight the config file once * before reading it _again_ in the main loop. * This allows things, log files configuration * for example, to settle down. */ So, post_config hooks are always called twice. You can see a working example in modules/mappers/mod_rewrite.c or in modules/generators/mod_cgid.c: there you'll find a flag called "first_time" in the post_config/cgid_init handler which takes care of the number of passes. Cheers, Erik
Re: cvs commit: httpd-2.0/docs/manual/misc relevant_standards.html.en relevant_standards.xml
On 19/09/2003, at 08:45, André Malo wrote: Roy T. Fielding wrote: http://www.rfc-editor.org/rfc/rfc2617.txt";>RFC 2617 - (Draft standard) + (Standards Track) IETF standards track: Internet Draft < Proposed Standard < Draft Standard < Standard 2617 is a Draft Standard, like 2616. Doh, sorry. Can someone please ( re-)correct it? I have currently no cvs access from here... Thanks. nd Done. Cheers, Erik
Re: ScriptLog
On 06/09/2003, at 11:43, Astrid Keßler wrote: Cliff wrote: Yes, it would. But for a debug log it's a price I'm willing to accept. Just an unformed idea: allow these directives within (and ?), but not within .htaccess files. The log file could be opened as usual. Hmm, yeah, but this won't help with the problem Cliff is facing, I guess: he is probably logged into apache.org and wants to debug a script he's developing right now, so (pre-)enabling it in the server config makes no sense. It'd be really nice to have the possibility to enable script/rewrite logging 'on the fly' without any changes to the config, besides a AllowOverride option (and with the downside of opening/closing the logfile per request). Or do you possibly think about something similar to the following: ScriptAlias /cgi-bin/ ... ScriptLog ... ScriptLogBuffer ... where you'd have a dedicated sub directory to test your scripts. Hmm, why not? Cheers, Erik Kess
Re: Time for 2.2?
On 31/08/2003, at 09:21, Sander Striker wrote: Indeed. Since 2.2 is already about the AAA rewrite it would be nice to include the final step on that subject aswell. Thoughts? -- justin What about: I'll do a 2.1 release at the same time as 2.0.48? Just to prevent any misunderstandings: are we talking about a 2.2 *alpha* or *beta* release here, or what will it be called? If it's in any way marked as *unstable*, then a clear +1 from my side. The recent changes are definitely worth to get tested in the wild, IMHO. A X.Y release where X and especially Y > 0 is often perceived as a major bug fix release in my experience (fwiw) and I'd like to ensure that nobody is expecting too much... hmm, but perhaps I'm too fussy about this? Cheers, Erik Sander
Re: Apache 2.0.47 Windows SSL
On 25/07/2003, at 06:07, Henri Gomez wrote: Hi to all, Did some of you have a binary for mod_ssl 2.0.47 Windows ? There is a 'over-complete' pre-built Apache 2.0.47 package including mod_ssl and OpenSSL 0.9.7b for Windows: http://www.apachefriends.org/wampp.html But be aware that it's fairly large, around 43MB. Didn't look into it; just stumbled over it recently... Cheers, Erik Regards
Re: configuring an ODBC database with JNDI
On 25/07/2003, at 02:10, dein_metzger wrote: hi everybody. I am new to the list. and to JSP and JavaBeans I would like to know how i configure an ODBC database called "inicio" to work with JNDI, and how I use it in my JSP / Javabean. (I am using tomcat 4.1 on windows xp) Sorry, but this is the developer list for the Apache HTTP Server Project. It seems, you're searching for a Tomcat-specific user-list or perhaps other Java / Jakarta related lists. Have a look here: http://jakarta.apache.org/site/mail.html http://jakarta.apache.org/site/mail2.html#Tomcat Cheers, Erik thanks in advance, InacioW-
Re: Offering modules for core httpd distro
On 24/07/2003, at 11:45, André Malo wrote: Looks like we get closer to the point we should develop a CAHSMAN [1]. Spare time available somewhere? :) just fyi: there's a discussion about a possible revamp of modules.apache.org going on on [EMAIL PROTECTED] and irc://#apache-modules. Under consideration are the following topics: site design, possible new features, backend clean-up/enhancements, etc... perhaps this is a starting point :) Cheers, Erik Ahh, and WRT Nicks module offer, I completely agree with you, nd. nd [1] Comprehensive Apache HTTP Server Module Archive Network ...
Re: cvs commit: httpd-2.0/docs/manual/vhosts details.html.en details.html.ko.euc-krexamples.html.en examples.html.ko.euc-kr fd-limits.html.en fd-limi
Justin Erenkrantz wrote: Even if we don't drop the generated files in the repository (which I won't really comment on, other than that Java on FreeBSD isn't very stable - which matters because daedalus is on FreeBSD - someone may want to try to generate the docs on daedalus itself), I think the best overall solution would be to alter the CVS mailer script to send ViewCVS URLs to all of the files that changed when the entire diff exceeds a certain limit. Commits that exceed the mailing list threshold are dropped and that's not good *ever*. I imagine some Perl hacker could tweak logaccum.pl to do this (/home/cvs/CVSROOT/log_accum.pl). If not, well, it might be time to rewrite logaccum.pl into Python. =) -- justin I just submitted a patch for log_accum.pl to infrastructure@, which does exactly this. Resulting mail msg exceeds predefined size limit -> ViewCVS URLs Resulting mail msg doesn't exceed predefined size limit -> full-featured diff as normal No dropped commit mails, all fine :) Cheers, Erik BTW, AFAICT somebody recently had the same problem on Xerces-C, so this is not only an issue with our we-store-all-and-everything docs tree :-)
Re: cvs commit: httpd-2.0/modules/ssl mod_ssl.c
Thanks, Justin! Cheers, Erik [EMAIL PROTECTED] wrote: jerenkrantz2003/05/31 12:29:47 Modified:modules/ssl mod_ssl.c Log: Revert revision 1.81 which called non-existent SSL_load_library. No idea where this was seen, but OpenSSL 0.9.7b does not have this. This gets mod_ssl working again. Revision ChangesPath 1.82 +1 -1 httpd-2.0/modules/ssl/mod_ssl.c Index: mod_ssl.c === RCS file: /home/cvs/httpd-2.0/modules/ssl/mod_ssl.c,v retrieving revision 1.81 retrieving revision 1.82 diff -u -u -r1.81 -r1.82 --- mod_ssl.c 30 May 2003 21:35:04 - 1.81 +++ mod_ssl.c 31 May 2003 19:29:47 - 1.82 @@ -240,7 +240,7 @@ */ CRYPTO_malloc_init(); ERR_load_crypto_strings(); -SSL_load_library(); +OpenSSL_add_all_algorithms(); #if HAVE_ENGINE_LOAD_BUILTIN_ENGINES ENGINE_load_builtin_engines(); #endif
Re: cvs commit: httpd-2.0/modules/ssl mod_ssl.c
Hmmm, but apps/apps.h and some example apps (rsautl.c, pkcs8.c) are using OpenSSL_add_all_algorithms() instead of SSL_load_library() and furthermore it seems that the complete source tree (0.9.6 & 0.9.7 CVS HEAD of yesterday) lacks any reference to SSL_load_library()?! Perhaps I'm blind but building 2.1 together with mod_ssl and OpenSSL 0.9.7b is currently broken for me: modules/ssl/.libs/mod_ssl.al(mod_ssl.lo)(.text+0x26): In function `ssl_hook_pre_config': /tmp/httpd-install/modules/ssl/mod_ssl.c:243: undefined reference to `SSL_load_library' Cheers, Erik [EMAIL PROTECTED] wrote: wrowe 2003/05/30 14:35:55 Modified:modules/ssl mod_ssl.c Log: OpenSSL_add_all_algorithms is simply an alias for SSL_load_library. Note that the entire schema of what-we-load-how follows from OpenSSL 0.9.7's own apps/ example applications. More review is greatly desired, but that's where I believed I should start looking for the 'correct' order of operations. Revision ChangesPath 1.81 +1 -1 httpd-2.0/modules/ssl/mod_ssl.c Index: mod_ssl.c === RCS file: /home/cvs/httpd-2.0/modules/ssl/mod_ssl.c,v retrieving revision 1.80 retrieving revision 1.81 diff -u -r1.80 -r1.81 --- mod_ssl.c 30 May 2003 20:58:55 - 1.80 +++ mod_ssl.c 30 May 2003 21:35:04 - 1.81 @@ -240,7 +240,7 @@ */ CRYPTO_malloc_init(); ERR_load_crypto_strings(); -OpenSSL_add_all_algorithms(); +SSL_load_library(); #if HAVE_ENGINE_LOAD_BUILTIN_ENGINES ENGINE_load_builtin_engines(); #endif
Re: Fixed [Fwd: Re: PR 8889: 1.3 apidoc is broken and I don't knowhow to fix :)]
André Malo wrote: * Erik Abele wrote: Just pinging another (the 3rd time)... perhaps now somebody can have a look at this. Been there, done that. Works perfect now. Thanks for the reminder ;-) nd Thanks, André! cheers, Erik
Fixed [Fwd: Re: PR 8889: 1.3 apidoc is broken and I don't know howto fix :)]
Just pinging another (the 3rd time)... perhaps now somebody can have a look at this. It's all fixed and in CVS but I don't have enough karma to fix this by myself :( cheers, Erik HINT: if nobody has the feeling to fix this just because its 1.3, then please give me access to daedalus and I will go and fix it :-> Original Message Subject: Re: PR 8889: 1.3 apidoc is broken and I don't know how to fix Date: Sat, 01 Mar 2003 17:34:48 +0100 From: Erik Abele <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED] References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> André Malo wrote: > * André Malo wrote: > >> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8889 >> >> All the links inside of the text are causing 404s (missing >> apidoc_prefix and .html suffix). Where is that stuff stored >> and generated? Although it's 1.3 we should keep it clean :) > > hmm. It seems, I'm not the right person to fix that. Can > someone with more knowledge about that fun explain me how to > the actual online apidoc is/was built or much better, > fix it? ;-)) I've fixed that in cvs:/site-tools/httpd-docs/APIdict.pm r1.6 but I don't have a clue how this gets on the website. I guess it's checked out into the appropriate dir on daedalus and then built over there, but since I don't have an account on daedalus, we'll need somebody else to fix this :) Can anybody please take the required steps and update the website (http://httpd.apache.org/dev/apidoc/)? You'll need the following: - cvs:/httpd-docs-1.3/apidoc/* - cvs:/site-tools/httpd-docs/APIdict.pm - cvs:/site-tools/httpd-docs/mkapidict and then execute ./mkapidict -l0 -d api.list -o index.html -t api-dict.html -v TIA and cheers, Erik -- - - - - - - - - - - - - - - - - - - - - - - Erik Abele ~ http://www.codefaktor.de/ [EMAIL PROTECTED] ~ [EMAIL PROTECTED] - - - - - - - - - - - - - - - - - - - - - -
Re: Backport problem
William A. Rowe, Jr. wrote: I see we've pushed to cvs HEAD of httpd-2.0 - and we are most broken. Please back us down to tag APACHE_2_0_BRANCH!!! For example, http://cvs.apache.org/viewcvs/httpd-2.0/docs/platform/ tries to returns a content-type: application/x-httpd-cgi there isn't a docs/platform subdirectory, try instead http://cvs.apache.org/viewcvs/httpd-2.0/docs/manual/platform/ btw, the body of the response equipped with a content-type of application/x-httpd-cgi actually contains the error msg: '/viewcvs.cgi/httpd-2.0/docs/platform/: unknown location' if you call it with viewcvs.cgi instead of only viewcvs you'll get a correct content-type of text/plain :-) hmmm HTH, erik Bill
[Fwd: Re: PR 8889: 1.3 apidoc is broken and I don't know how to fix:)]
Just pinging another time... perhaps somebody can have a look at this. It's all fixed and in CVS but I don't have enough karma (and knowledge) to fix this by myself :( cheers, Erik Original Message Subject: Re: PR 8889: 1.3 apidoc is broken and I don't know how to fix Date: Sat, 01 Mar 2003 17:34:48 +0100 From: Erik Abele <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED] References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> André Malo wrote: * André Malo wrote: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8889 All the links inside of the text are causing 404s (missing apidoc_ prefix and .html suffix). Where is that stuff stored and generated? Although it's 1.3 we should keep it clean :) hmm. It seems, I'm not the right person to fix that. Can someone with more knowledge about that fun explain me how to the actual online apidoc is/was built or much better, fix it? ;-)) I've fixed that in cvs:/site-tools/httpd-docs/APIdict.pm r1.6 but I don't have a clue how this gets on the website. I guess it's checked out into the appropriate dir on daedalus and then built over there, but since I don't have an account on daedalus, we'll need somebody else to fix this :) Can anybody please take the required steps and update the website (http://httpd.apache.org/dev/apidoc/)? You'll need the following: - cvs:/httpd-docs-1.3/apidoc/* - cvs:/site-tools/httpd-docs/APIdict.pm - cvs:/site-tools/httpd-docs/mkapidict and then execute ./mkapidict -l0 -d api.list -o index.html -t api-dict.html -v TIA and cheers, Erik -- - - - - - - - - - - - - - - - - - - - - - - Erik Abele ~ http://www.codefaktor.de/ [EMAIL PROTECTED] ~ [EMAIL PROTECTED] - - - - - - - - - - - - - - - - - - - - - -
Re: how to get 2.0.45-dev ?
> From: Günter Knauf <[EMAIL PROTECTED]> > > Hi, > just wanted to compile 2.0.45 (need it because of 3rd-party module lower MMN) > but I dont know how to get it: > - http://cvs.apache.org/snapshots/ has only 2.1-dev, but its named 2.0 > - http://cvs.apache.org/viewcvs.cgi/ also only shows 2.1-dev, but named > httpd-2.0 > - cvs -d :pserver:[EMAIL PROTECTED]:/home/cvspublic co httpd-2.0 also > returns 2.1-dev > you'll have to check out the 2.0 branch instead of HEAD: cvs -d :pserver:[EMAIL PROTECTED]:/home/cvspublic co -d httpd-2.0.45 -r APACHE_2_0_BRANCH httpd-2.0 (one line, my MUA unfortunately wraps lines) cheers, Erik > so how can I get current 2.0-stable ?? > and: wouldnt it make sense to rename all these 2.0 to 2.1 to avoid confusion?? > and would be nice to have 2.0-stable also as snapshots... > > Guenter. >
Re: place for suggestions
> From: Günter Knauf <[EMAIL PROTECTED]> > > Hi, > I was just asked where a user should send his suggestion for new features he's > missing in Apache? Should it go into BugZilla? An issue filed in bugzilla and marked as enhancement should be fine IMHO. cheers, Erik > Guenter.
Re: PR 8889: 1.3 apidoc is broken and I don't know how to fix :)
André Malo wrote: * André Malo wrote: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8889 All the links inside of the text are causing 404s (missing apidoc_ prefix and .html suffix). Where is that stuff stored and generated? Although it's 1.3 we should keep it clean :) hmm. It seems, I'm not the right person to fix that. Can someone with more knowledge about that fun explain me how to the actual online apidoc is/was built or much better, fix it? ;-)) I've fixed that in cvs:/site-tools/httpd-docs/APIdict.pm but I don't have a clue how this gets on the website. I guess it's checked out into the appropriate dir on daedalus and then built over there, but since I don't have an account on daedalus, we'll need somebody else to fix this :) Can anybody please take the required steps and update the website (http://httpd.apache.org/dev/apidoc/)? You'll need the following: - cvs:/httpd-docs-1.3/apidoc/* - cvs:/site-tools/httpd-docs/APIdict.pm - cvs:/site-tools/httpd-docs/mkapidict and then execute ./mkapidict -l0 -d api.list -o index.html -t api-dict.html -v TIA and cheers, Erik
Re: [PATCH] Re: Apache 2.0 download problem
Greg Ames wrote: D'oh! I must have fat fingered it somehow. Sorry. (writes 50 times on the whiteboard: I will do "cvs diff" before "cvs commit" I will do "cvs diff" before "cvs commit" I will do "cvs diff" before "cvs commit" etc) Hehe, recently I needed three attempts to get a simple two-line commit right :-> OK, it should be correct on daedalus now. Thanks for the review and for the second patch. great, thanks too. cheers, Erik
Re: PR 8889: 1.3 apidoc is broken
AFAIK the corresponding data files can be found in the httpd-docs-1.3 module [1]. See the messages-?.xml files as well as the apidoc subdir. The scripts to generate the whole stuff are located in the httpd-docs subdir in the site-tools module [2]. cheers, Erik [1] http://cvs.apache.org/viewcvs.cgi/httpd-docs-1.3/ [2] http://cvs.apache.org/viewcvs.cgi/site-tools/httpd-docs/ André Malo wrote: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8889 All the links inside of the text are causing 404s (missing apidoc_ prefix and .html suffix). Where is that stuff stored and generated? Although it's 1.3 we should keep it clean :) nd
[PATCH] Re: Apache 2.0 download problem
Greg Ames wrote: Erik Abele wrote: Therefore I sent the attached patch some days ago ;-) Patch applied and that directory cvs up'd on daedalus. Thanks, Erik. What I didn't do (and your patch didn't do either) is change the reference in README.html to a "small patch for a small problem" pointing to apache_2.0.43-win9x-x86-apr-patch.zip . I don't know for certain if that is relevant for .44, but there is a .44 patch with that naming convention, so maybe there is another small problem. Could someone who knows for sure what's going on here please do whatever is appropriate? My patch didn't include it because it was already correct :-) It said '...is called apache_2.0.44-win9x-x86-apr-patch.zip' which is correct (the appropriate file is there, see also Joshua's commit -> r1.32). Now it says: '...is called apache_2.0.43-win9x-x86-apr-patch.zip' which is not correct IMHO, there is no file with such a name. Find below another patch to get it finally right (also linked to the mentioned patch for clarity)... cheers, Erik Thanks, Greg Index: README.html === RCS file: /home/cvs/httpd-dist/binaries/win32/README.html,v retrieving revision 1.33 diff -u -r1.33 README.html --- README.html 28 Feb 2003 17:13:27 - 1.33 +++ README.html 28 Feb 2003 20:35:35 - @@ -93,9 +93,9 @@ Due to a small problem in this release, Win95/98/ME users must download, in addition to the regular distribution, a small patch file containing an updated bin/libapr.dll file. The file -is called apache_2.0.43-win9x-x86-apr-patch.zip -and should be extracted from the root of your Apache installation. - +is called apache_2.0.44-win9x-x86-apr-patch.zip and should be +extracted from the root of your Apache installation. A full setup package (.exe) containing the Win9x/WinNT Microsoft System Installer installer is now available. If the Microsoft System Installer
Re: Apache 2.0 download problem
> Got a ton of those lately... It's proably because > http://nagoya.apache.org/mirror/httpd/binaries/win32/ > > Advertises that the last stable version is 2.0.43, while in the files we > have 2.0.44... Therefore I sent the attached patch some days ago ;-) Can somebody please apply it to the httpd-dist repo or alternatively give me enough karma to do it by myself. BTW, I just noticed that the README.html/HEADER.html files are showing up in the file list on www.apache.org/dist/httpd/ (et al.). I think this was due to perl.apache.org's ordinary README files, but I wonder if we couldn't handle this selectively for httpd-dist (.htaccess: IndexIgnore ...) and hide 'em ? cheers, Erik > > Pier > > > > > -- Forwarded Message > From: "Daniel Trifonov" <[EMAIL PROTECTED]> > Reply-To: <[EMAIL PROTECTED]> > Date: Fri, 28 Feb 2003 03:20:50 -0800 > To: <[EMAIL PROTECTED]> > Subject: Apache 2.0 download problem > > > Hi Pier, > > I've just tried to download the last distribution of the Apache web server > (for Win32) from several download mirrors (including your servers), but the > link to the distribution package httpd-2.0.43-win32-src.zip seems to be > broken! Where can I get the software? > > > > Free 20MB Web Site Hosting and Personalized E-mail Service! > Get It Now At Doteasy.com http://www.doteasy.com/et/ > > > > -- End of Forwarded Message Index: binaries/win32/HEADER.html === RCS file: /home/cvspublic/httpd-dist/binaries/win32/HEADER.html,v retrieving revision 1.28 diff -u -r1.28 HEADER.html --- binaries/win32/HEADER.html 3 Oct 2002 15:12:16 - 1.28 +++ binaries/win32/HEADER.html 24 Feb 2003 12:35:50 - @@ -6,7 +6,7 @@ Windows 95 Apache Users Read This First Windows XP Apache Users Read This First ZoneAlarm (or other firewall) Users Read This First -The current stable release is Apache 2.0.43 +The current stable release is Apache 2.0.44 The old stable release is Apache 1.3.27 MSI Binary Distribution Packages Troubleshooting MSI Installation Problems Index: binaries/win32/README.html === RCS file: /home/cvspublic/httpd-dist/binaries/win32/README.html,v retrieving revision 1.32 diff -u -r1.32 README.html --- binaries/win32/README.html 22 Jan 2003 16:19:28 - 1.32 +++ binaries/win32/README.html 24 Feb 2003 12:35:51 - @@ -82,7 +82,7 @@ responsibility to determine the compatibility between any firewall product and the Apache HTTP Server. -The current stable release is Apache 2.0.43 +The current stable release is Apache 2.0.44 Apache 2.0 is released for General Availability. @@ -110,8 +110,8 @@ Because the distribution tree has changed, we haven't yet identified an effective way to incorporate the source tree into the binary distribution. - You will find the source package in /dist/httpd/httpd-2.0.43-win32-src.zip. That -win32-src.zip file contains + You will find the source package in /dist/httpd/httpd-2.0.44-win32-src.zip. That -win32-src.zip file contains only source and build files, and contains no binaries.
[PATCH] httpd-dist typos
Can somebody please apply the attached patch to the httpd-dist repo (or alternatively give me karma); there are just some 2.0.43's instead of 2.0.44's ;-) BTW, I just noticed that the README.html/HEADER.html files are showing up in the file list on www.apache.org/dist/httpd/ (et al.). I think this was due to perl.apache.org's ordinary README files, but I wonder if we couldn't handle this selectively for httpd-dist (.htaccess: IndexIgnore ...) and hide 'em ? cheers, Erik Index: binaries/win32/HEADER.html === RCS file: /home/cvspublic/httpd-dist/binaries/win32/HEADER.html,v retrieving revision 1.28 diff -u -r1.28 HEADER.html --- binaries/win32/HEADER.html 3 Oct 2002 15:12:16 - 1.28 +++ binaries/win32/HEADER.html 24 Feb 2003 12:35:50 - @@ -6,7 +6,7 @@ Windows 95 Apache Users Read This First Windows XP Apache Users Read This First ZoneAlarm (or other firewall) Users Read This First -The current stable release is Apache 2.0.43 +The current stable release is Apache 2.0.44 The old stable release is Apache 1.3.27 MSI Binary Distribution Packages Troubleshooting MSI Installation Problems Index: binaries/win32/README.html === RCS file: /home/cvspublic/httpd-dist/binaries/win32/README.html,v retrieving revision 1.32 diff -u -r1.32 README.html --- binaries/win32/README.html 22 Jan 2003 16:19:28 - 1.32 +++ binaries/win32/README.html 24 Feb 2003 12:35:51 - @@ -82,7 +82,7 @@ responsibility to determine the compatibility between any firewall product and the Apache HTTP Server. -The current stable release is Apache 2.0.43 +The current stable release is Apache 2.0.44 Apache 2.0 is released for General Availability. @@ -110,8 +110,8 @@ Because the distribution tree has changed, we haven't yet identified an effective way to incorporate the source tree into the binary distribution. - You will find the source package in /dist/httpd/httpd-2.0.43-win32-src.zip. That -win32-src.zip file contains + You will find the source package in /dist/httpd/httpd-2.0.44-win32-src.zip. That -win32-src.zip file contains only source and build files, and contains no binaries.
Re: Where to start from?
You might want to try the Apache Modelling Portal [http://apache.hpi.uni-potsdam.de/] and it's main doc http://apache.hpi.uni-potsdam.de/modules.php?name=Downloads&d_op=getit&lid=3 Perhaps my pretty old (but recently updated) linklist might be helpful too: http://www.codefaktor.de/misc/apachelinks.html Have look at the sections #Apache 1.3 Developer Resources and #Apache 2.0 Developer Resources. cheers, Erik ahh, and don't forget to actually read the source code :-) Chan Casey wrote: Hi, I want understand more about the internal design of Apache on the source code level. Can anyone provide some hints/info about where to start with, and the inter-relationship among different components of Apache? Thanks, any help is appreciated. CC ** *IMPORTANT NOTICE: * *This electronic message contains information, which may be confidential, privileged or otherwise protected from disclosure. The information is intended to be used solely by the recipient(s) named. If you are not an intended recipient, be aware that any review, disclosure, copying, distribution or use of this message or it's contents is prohibited. If you have received this message in error, please notify the sender and delete this message from your system. Employees of the company are prohibited from making defamatory statements and from infringing copyright or any other legal right. Any such communication or infringement is contrary to company policy and outside the scope of employment. * * *
Re: Patches and Enhancements for a SSL-Proxy Based on Apache 2.0 (mod_ssl, mod_proxy, mod_headers)
Hi Maik, > And here follows the patch (My proposed changes to the HTML docu are now not > included in the patch. Please advice me if and how to post this changes to > mod_headers.html.en) Just post it here or to the docs-list ([EMAIL PROTECTED]) as a unified diff patch (diff -u). But please be aware, that we are generating the whole documentation from XML source. Therefore you should patch these instead of the HTML files. More information is available at http://httpd.apache.org/docs-project/docsformat.html cheers, Erik
Re: merging httpd-pop3 into httpd-2.0?
Jim Jagielski wrote: Erik Abele wrote: Perhaps there is not much interest because it is somewhat 'hidden'? IMHO mod_pop3 would gain more visibility and therefore perhaps a better community when folded into httpd. Imagine windoze users: they mostly rely on binary distributions and up to now there are just the sources around. If mod_pop3 gets used more widely, there probably will be also more developers who will be attracted to contribute. Leaving it in it's own repo-module as it is now, without any person in charge of it, will let it die on the long run. Personally I'm +/-0 towards folding it into httpd, since I won't have the time to contribute...just my 2c. Once again, I'm +1 in getting it moved in. It's an example of an protocol module. It's a good module. It's a worthwhile module. It would benefit from more people working on it, and people are interested in doing so. Well, than let's move it in. A quick overview of the last mails shows the following votes: justin +0 modules/pop3 jim +1 modules/experimental bills -0 !modules/pop3 willrowe -0 modules/experimental / +0 modules/pop / +1 for it's current repository plus some positive votes from Daniel Lopez, Thomas Eibner, Harrie Hazwinkel and Chris Taylor. As far as I'm concerned I will change my +/-0 to a +1 and would like to see it in modules/experimental. Perhaps we should have a binding vote and then proceed? What has to be done? As Jim pointed out, the licence issues so far are intact... cheers, erik
Re: merging httpd-pop3 into httpd-2.0?
Harrie Hazewinkel wrote: HI, On Saturday, January 25, 2003, at 10:22 PM, Justin Erenkrantz wrote: --On Saturday, January 25, 2003 9:43 PM +0100 Harrie Hazewinkel <[EMAIL PROTECTED]> wrote: 3)Why for instance, could this not stay as a seperate module?? The case that can be made for folding it in is that there is no community currently around mod_pop3. If people were to step up and be responsible for it outside of the main tree, then I don't think there'd be a desire to merge it in. I see it different. Currently their is no interest in it, so there is no reason to fold it in. People are not interested in it and thus it would just consuming extra bytes in an HTTPD distribution. Perhaps there is not much interest because it is somewhat 'hidden'? IMHO mod_pop3 would gain more visibility and therefore perhaps a better community when folded into httpd. Imagine windoze users: they mostly rely on binary distributions and up to now there are just the sources around. If mod_pop3 gets used more widely, there probably will be also more developers who will be attracted to contribute. Leaving it in it's own repo-module as it is now, without any person in charge of it, will let it die on the long run. Personally I'm +/-0 towards folding it into httpd, since I won't have the time to contribute...just my 2c. cheers, erik
Segfault in 2.1 head on linux
After building the current Apache 2.1 & APR HEAD I hit a segfault by starting the server. A quick gdb session shows problems in apr_file_open at apr/file_io/unix/open.c:149
---
(gdb) run -X
Starting program: /usr/sbin/httpd -X
[New Thread 1024 (LWP 21251)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1024 (LWP 21251)]
0x401ef78d in apr_file_open (new=0xb59c,
fname=0x8147078 "/etc/httpd/conf/httpd.conf", flag=129, perm=4095,
pool=0x80ff8d0) at open.c:149
149 if ((flag & APR_BUFFERED) && ((*new)->flags & APR_XTHREAD)) {
(gdb) bt
#0 0x401ef78d in apr_file_open (new=0xb59c,
fname=0x8147078 "/etc/httpd/conf/httpd.conf", flag=129, perm=4095,
pool=0x80ff8d0) at open.c:149
#1 0x080b71d8 in ap_pcfg_openfile (ret_cfg=0xb638, p=0x80ff8d0,
name=0x8147078 "/etc/httpd/conf/httpd.conf") at util.c:910
#2 0x080b2e52 in ap_process_resource_config (s=0x8106320,
fname=0x8147078 "/etc/httpd/conf/httpd.conf", conftree=0x80f2354,
p=0x80ff8d0, ptemp=0x81439e0) at config.c:1545
#3 0x080b352f in ap_read_config (process=0x80fd948, ptemp=0x81439e0,
filename=0x80e2abb "/etc/httpd/conf/httpd.conf", conftree=0x80f2354)
at config.c:1832
#4 0x080b5130 in main (argc=2, argv=0xb8e4) at main.c:565
#5 0x42017589 in __libc_start_main () from /lib/i686/libc.so.6
(gdb) print (*new)->flags
Cannot access memory at address 0xc
(gdb) print (*new)
$2 = (apr_file_t *) 0x0
---
seems that this has something to do with the latest changes in apr/file_io/unix/open.c... the following patch works fine for me.
--- /home/cvs/apr/file_io/unix/open.c Mon Dec 30 02:58:01 2002
+++ open.c Mon Dec 30 03:59:26 2002
@@ -146,7 +146,7 @@
#endif
#if APR_HAS_THREADS
-if ((flag & APR_BUFFERED) && ((*new)->flags & APR_XTHREAD)) {
+if ((flag & APR_BUFFERED) && (flag & APR_XTHREAD)) {
rv = apr_thread_mutex_create(&thlock,
APR_THREAD_MUTEX_DEFAULT, pool);
if (rv) {
also does reverting open.c to rev. 1.101.
cheers,
erik
Re: [Review] MPM docs revision
> Von: Enrico Weigelt <[EMAIL PROTECTED]> > Antworten an: [EMAIL PROTECTED] > Datum: Tue, 17 Dec 2002 06:30:55 +0100 > An: [EMAIL PROTECTED] > Betreff: Re: [Review] MPM docs revision > > On Tue, Dec 17, 2002 at 03:09:58AM +0100, André Malo wrote: > > > >> - added new docs for beos, leader, mpmt_os2 and threadpool. >> The descriptions are mainly taken from the READMEs and/or code comments. > > i'll post some stuff about my new mpm in some days ... > > btw: are there manpages for the apache configuration ? > We removed the available manpages for apachectl & httpd since there is nobody who is able to maintain and update the nroff stuff (see http://cvs.apache.org/viewcvs.cgi/httpd-docs-2.0/man/) You can find the updated XML/HTML versions online at http://httpd.apache.org/docs-2.0/programs/httpd.html and http://httpd.apache.org/docs-2.0/programs/apachectl.html HTH, erik
Re: [PATCH] ServerSignature privacy - option 1
Francis Daly wrote: On Sat, Nov 02, 2002 at 11:29:29AM -0800, Justin Erenkrantz wrote: And, if you could submit a patch for the documentation, that'd be appreciated. =) ... The other is for httpd-docs-2.0/manual/mod/core.xml, which adds an extra comment to the two directives. Also against the most recent CVS version; hopefully I've got the style correct. no problem here, the patch is fine for the docs. Perhaps we should add a nice red border to make it easier to find the info. I will do that when the patches are actually committed. erik
Re: new download page
Joshua Slive wrote: Erik Abele wrote: +1. great idea, but I think the mirror sites should be mentioned more than only once. Perhaps an extra paragraph like the following would help: If you look at the actual links, you'll see I'm pretty much forcing people to download from the mirrors. I provide direct links only to the mirrors. I do provide a link to the main site at the top, but I think most people will take the direct links. Oh sorry, I didn't realize that. I only saw the pointers in the text. Well, then forget the extra paragraph, all this should be sufficient ;-) Another Point are the official patches. IMO we should mention http://www.apache.org/dist/httpd/patches/ together with a little note: "When we have patches to a minor bug or two, or features which we haven't yet included in a new release, we will put them in the patches subdirectory so people can get access to it before we roll another complete release."[1] Perhaps a short note in the top section. But there is rarely anything interesting in the patches directory. That is, what I thought of... Isn't the above note short enough? oh, btw the 2.0 paragraph praises 2.0.36 as the best available version instead of 2.0.43. The headline, the text and the check-for-patches-link are wrong. Yep, thanks, I copied my text from a non-updated version of the dist/README.html. I'll fix that. Joshua. erik
Re: new download page
Joshua Slive wrote: http://httpd.apache.org/download.html I believe this is better than the current circumstances because it is clearer for the users, and it better enables us to direct people to the mirrors for the download and the main site for the signatures. I've never particularly like the autoindex/README/HEADER thing. It is consfusing trying to figure out exactly what to download and there are notes scattered all over the place. And it works very poorly on the mirrors, since many of them are not configured in exactly the same was as www.apache.org. I will be changing the links on httpd.apache.org to point to this page instead of directly at http://www.apache.org/dist/httpd/. I'll wait a day for corrections and comments. I believe this should go a long way towards reducing daedelus bandwidth usage for httpd downloads. It will, of course, do nothing for jakarta/xml/etc. Joshua. +1. great idea, but I think the mirror sites should be mentioned more than only once. Perhaps an extra paragraph like the following would help: "Please do not download from www.apache.org. Please use a mirror site to help us save apache.org bandwidth. Go here to find your nearest mirror."[1] Another Point are the official patches. IMO we should mention http://www.apache.org/dist/httpd/patches/ together with a little note: "When we have patches to a minor bug or two, or features which we haven't yet included in a new release, we will put them in the patches subdirectory so people can get access to it before we roll another complete release."[1] oh, btw the 2.0 paragraph praises 2.0.36 as the best available version instead of 2.0.43. The headline, the text and the check-for-patches-link are wrong. cheers, erik [1] taken from http://www.apache.org/dist/httpd/
Re: [PATCH] mod_negotiation.c
William A. Rowe, Jr. wrote: At 07:44 PM 10/25/2002, you wrote: [ Simply trying again; or according to Jeff: nag, nag, nag ;-) ] If you use the "body" feature in type map files, the MIME-headers currently are set dependant on what (mostly) type_checker says about the type map file. The attached patch sets the MIME-type, charset, content-language and content-encoding of a negotiated type-map body. Thus you can hold different types, languages etc. inside the same file, for example: Nice! Thanks, I'll look and commit soon if nobody beats me to it. Wooha, that would be nice! so I can finally commit some exotic error-documents to get successfully negotiated :-) Thanks, Andre & Bill Erik
Re: [PATCH] (X)HTML-ouput in proxy_util.c
> Erik Abele wrote: > >> While browsing through the source I discovered a place in >> proxy_util.c (line 612), where the output isn't XHTMLized so far. >> >> Since all other server-generated output and the error documents are >> valid XHTML, I think >> we should change this too. Attached a patch for review please. Are >> there any objections to not apply this? I don't think so...:-) wuups, sorry, I forgot to attach the patch :-) Erik Index: proxy_util.c === RCS file: /home/cvs/httpd-2.0/modules/proxy/proxy_util.c,v retrieving revision 1.97 diff -u -r1.97 proxy_util.c --- proxy_util.c15 Jul 2002 08:05:10 - 1.97 +++ proxy_util.c25 Aug 2002 14:07:36 - @@ -612,13 +612,13 @@ apr_table_setn(r->notes, "error-notes", apr_pstrcat(r->pool, "The proxy server could not handle the request " - "pool, r->uri), + "pool, r->uri), "\">", ap_escape_html(r->pool, r->method), " ", - ap_escape_html(r->pool, r->uri), ".\n" - "Reason: ", + ap_escape_html(r->pool, r->uri), ".\n" + "Reason: ", ap_escape_html(r->pool, message), - "", NULL)); + "", NULL)); /* Allow "error-notes" string to be printed by ap_send_error_response() */ apr_table_setn(r->notes, "verbose-error-to", apr_pstrdup(r->pool, "*"));
[PATCH] (X)HTML-ouput in proxy_util.c
While browsing through the source I discovered a place in proxy_util.c (line 612), where the output isn't XHTMLized so far. Since all other server-generated output and the error documents are valid XHTML, I think we should change this too. Attached a patch for review please. Are there any objections to not apply this? I don't think so...:-) Erik
Re: [PATCH] XHTML1.1 Error-Docs
Hi Joshua. > Thanks! I commited your patch with the sole change that I removed the > meta-content-type header, which is just bad news in my opinion. I'm a little bit unsure about the meta-content-type header: the XHTML 1.0 specification (http://www.w3.org/TR/xhtml1/) recommends to use both methods to define the content-type on existing/older user agents. an extract of REC-xhtml1-2126 follows: === Snip Appendix C. HTML Compatibility Guidelines This appendix is informative. This appendix summarizes design guidelines for authors who wish their XHTML documents to render on existing HTML user agents ... C.9 Character Encoding To specify a character encoding in the document, use both the encoding attribute specification on the xml declaration (e.g. ) and a meta http-equiv statement (e.g. ). The value of the encoding attribute of the xml processing instruction takes precedence. === Snip Maybe we should put the meta-header in again ? > > By the way, a repost on the docs list would have been just as effective. > whuups, thanks...I was unsure were to put this topic; sorry for that :-) regards, erik
[PATCH] XHTML1.1 Error-Docs
Hi!
Some weeks ago I posted the attached patch on the docs-list. Last week I
posted it a second time, but didn't receive any replies. Therefore I am
posting it here on the dev-list...
The patch modifies the present error doc templates (spacer.html, top.html,
bottom.html) to be valid XHTML 1.1 documents.
To ensure their correctness, I validated all the resulting error documents
(the ssi-parsed output) at w3.org.
I also had to correct the -tags in HTTP_INTERNAL_SERVER_ERROR.html.var
and an -tag in contact.html.var (see patch).
cheers,
erik
> Von: Justin Erenkrantz <[EMAIL PROTECTED]>
> An: [EMAIL PROTECTED]
> Betreff: Re: Valid XHTML Error-Docs
>
> On Wed, Jun 19, 2002 at 09:05:00PM +0200, Erik Abele wrote:
>> I would also prefer valid XHTML-Documents, but I don't want to convert all
>> the files if they won't be included.
>
> +1 especially if someone contributes them! -- justin
Index: httpd-docs-2.0/error/HTTP_INTERNAL_SERVER_ERROR.html.var
===
RCS file: /home/cvspublic/httpd-2.0/docs/error/HTTP_INTERNAL_SERVER_ERROR.html.var,v
retrieving revision 1.3
diff -u -I*.AppleDouble -r1.3 HTTP_INTERNAL_SERVER_ERROR.html.var
--- httpd-docs-2.0/error/HTTP_INTERNAL_SERVER_ERROR.html.var18 Jun 2002 22:34:34
- 1.3
+++ httpd-docs-2.0/error/HTTP_INTERNAL_SERVER_ERROR.html.var8 Jul 2002 18:04:48
+-
@@ -12,7 +12,7 @@
Fehlermeldung:
-
+
@@ -38,7 +38,7 @@
Error message:
-
+
@@ -65,7 +65,7 @@
Mensaje de error:
-
+
@@ -94,7 +94,7 @@
Message d'erreur:
-
+
Index: httpd-docs-2.0/error/contact.html.var
===
RCS file: /home/cvspublic/httpd-2.0/docs/error/contact.html.var,v
retrieving revision 1.5
diff -u -I*.AppleDouble -r1.5 contact.html.var
--- httpd-docs-2.0/error/contact.html.var 18 Jun 2002 22:34:34 - 1.5
+++ httpd-docs-2.0/error/contact.html.var 8 Jul 2002 18:04:48 -
@@ -1,24 +1,24 @@
Content-language: de
Content-type: text/html
Body:--de--
- Sofern Sie dies für eine Fehlfunktion des Servers halten,
- informieren Sie bitte den
- ">Webmaster
- hierüber.
+Sofern Sie dies für eine Fehlfunktion des Servers halten,
+informieren Sie bitte den
+">Webmaster
+hierüber.
--de--
Content-language: en
Content-type: text/html
Body:--en--
- If you think this is a server error, please contact
- the ">webmaster
+If you think this is a server error, please contact
+the ">webmaster
--en--
Content-language: es
Content-type: text/html
Body:--es--
Favor de contactar al
-">webmaster
+">webmaster
en caso de que usted crea que existe un error en el servidor.
--es--
@@ -26,5 +26,5 @@
Content-type: text/html
Body:--fr--
Si vous pensez qu'il s'agit d'une erreur du serveur, veuillez contacter
-le ">gestionnaire du
site
+le ">gestionnaire du
+site
--fr--
Index: httpd-docs-2.0/error/include/bottom.html
===
RCS file: /home/cvspublic/httpd-2.0/docs/error/include/bottom.html,v
retrieving revision 1.10
diff -u -I*.AppleDouble -r1.10 bottom.html
--- httpd-docs-2.0/error/include/bottom.html20 Jun 2002 03:51:46 - 1.10
+++ httpd-docs-2.0/error/include/bottom.html8 Jul 2002 18:04:49 -
@@ -1,19 +1,19 @@
-
+
-
+
-Error
-
-
-
-
-
+Error
+
+
+
+
+
-
-
+
-
-
-
-
+
+
+
+
+
Index: httpd-docs-2.0/error/include/spacer.html
===
RCS file: /home/cvspublic/httpd-2.0/docs/error/include/spacer.html,v
retrieving revision 1.1
diff -u -I*.AppleDouble -r1.1 spacer.html
--- httpd-docs-2.0/error/include/spacer.html19 Aug 2001 01:01:51 - 1.1
+++ httpd-docs-2.0/error/include/spacer.html8 Jul 2002 18:04:49 -
@@ -1 +1 @@
-
+
Index: httpd-docs-2.0/error/include/top.html
===
RCS file: /home/cvspublic/httpd-2.0/docs/error/include/top.html,v
retrieving revision 1.4
diff -u -I*.AppleDouble -r1.4 top.html
--- httpd-docs-2.0/error/include/top.html 21 Aug 2001 01:31:23 - 1.4
+++ httpd-docs-2.0/error/include/top.html 8 Jul 2002 18:04:49 -
@@ -1,11 +1,20 @@
-
-
-
-
-">
-
+
+http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd";>
+http://www.w3.org/1999/xhtml"; xml:lang="en">
+
+
+
+" />
+
+<!--
+body { color: #00; background-color: #FF; }
+a:link { color: #CC; }
+-->
+
+
-
-
-
-
+
+
+
+
