Re: Rolling 2.1.4...

2005-03-16 Thread Sander Striker
Sander Striker wrote:
Justin Erenkrantz wrote:
On Mon, Mar 14, 2005 at 08:03:43PM -0800, Paul Querna wrote:
I would like to roll the 2.1.4 alpha right after APR 1.1.1 is released.
I plan on rolling APR tonight or Tuesday morning.  If there arent any 
problems, I am hoping to create 2.1.4 on Thursday.  Any big 
outstanding issues?
As far as I can tell, the Win32 fixes still haven't been backported to 
APR 1.1.x.  Or, am I missing something?  -- justin
I'll go and look into this tonight if OtherBill *nudge* *nudge* doesn't 
beat
me to it.
FWIW, I've already gone ahead and tagged 2.1.4.  Work is now somewhat
getting in the way, so I'll get to rolling this afternoon.
Sander


Subrequests should not inherit entity-header fields from the mainline request

2005-03-16 Thread Bill Stoddard
Joe Schaefer wrote:
Greg Ames [EMAIL PROTECTED] writes:
[...]

As it turns out, we clone all of the main request's input headers when
we create the subrequest, including C-L.  Whacking the subrequest's
C-L header fixes the hang.  Since the main request's body could also
have be chunked, we should probably remove the subrequest's
Transfer-Encoding header as well. 

Shouldn't you remove Content-Type also?
The problem is that the subrequest is inheriting entity-header fields from the mainline request (mainline 
request was a POST). This patch should be generalised to remove all inherited entity-header fields from the 
subrequest.

Bill


Re: Subrequests should not inherit entity-header fields from the mainline request

2005-03-16 Thread Paul Querna
Bill Stoddard wrote:
Joe Schaefer wrote:
Greg Ames [EMAIL PROTECTED] writes:
[...]

As it turns out, we clone all of the main request's input headers when
we create the subrequest, including C-L.  Whacking the subrequest's
C-L header fixes the hang.  Since the main request's body could also
have be chunked, we should probably remove the subrequest's
Transfer-Encoding header as well. 

Shouldn't you remove Content-Type also?
The problem is that the subrequest is inheriting entity-header fields 
from the mainline request (mainline request was a POST). This patch 
should be generalised to remove all inherited entity-header fields from 
the subrequest.
Something that popped into my mind is, what about when you actually want 
to do a POST subrequest?

I think it would be quite hard with how subrequests are currently 
constructed.  I wish the all of the subrequest stuff could be refactored...

-Paul


Re: Subrequests should not inherit entity-header fields from the mainline request

2005-03-16 Thread Joe Schaefer
Paul Querna [EMAIL PROTECTED] writes:


[...]

 Something that popped into my mind is, what about when you actually
 want to do a POST subrequest?

This is exactly what I've been struggling with in apreq.
I think the only sane thing apreq can do is to assume that
subrequests will never have bodies attached (so no POST data
will ever be available to a subrequest via apreq).  I think
this is the original intent, and that the input filter cloning
is just there to prevent segfaults (e.g. the subrequest might 
install new filters for itself).
-- 
Joe Schaefer



2.1.4 available for testing

2005-03-16 Thread Sander Striker
Hi all,
There are some 2.1.4-alpha tarballs waiting to be tested at:
 http://httpd.apache.org/dev/dist/
Please report back with any problems.
Thanks for testing!
Sander


Re: 2.1.4 available for testing

2005-03-16 Thread Paul Querna
Sander Striker wrote:
Hi all,
There are some 2.1.4-alpha tarballs waiting to be tested at:
 http://httpd.apache.org/dev/dist/
Please report back with any problems.
Thanks for testing!
+1, Fedora Core 3.
-Paul


Re: 2.1.4 available for testing

2005-03-16 Thread Sander Striker
Sander Striker wrote:
Hi all,
There are some 2.1.4-alpha tarballs waiting to be tested at:
 http://httpd.apache.org/dev/dist/
Please report back with any problems.
Thanks for testing!
FWIW:  +1
Tested on:
 Linux (Ubuntu - Warty Warthog) 
 Win32 (XP SP2)*

Sander
*) Source from the tag, no zip ball is available at this time.


Re: 2.1.4 available for testing

2005-03-16 Thread Justin Erenkrantz
   --On Wednesday, March 16, 2005 10:00 PM +0100 Sander Striker 
[EMAIL PROTECTED] wrote:

Hi all,
There are some 2.1.4-alpha tarballs waiting to be tested at:
  http://httpd.apache.org/dev/dist/
Please report back with any problems.
+1 for beta on Darwin (modulo httpd-test issues from last time).
Thanks!  -- justin


Re: 2.1.4 available for testing

2005-03-16 Thread Graham Leggett
Sander Striker wrote:
There are some 2.1.4-alpha tarballs waiting to be tested at:
 http://httpd.apache.org/dev/dist/
+1 (RHEL3 RPMs)
Regards,
Graham
--


smime.p7s
Description: S/MIME Cryptographic Signature


Re: 2.1.4 available for testing

2005-03-16 Thread Brad Nicholes
+1 NetWare

Brad

 [EMAIL PROTECTED] Wednesday, March 16, 2005 2:00:47 PM 
Hi all,

There are some 2.1.4-alpha tarballs waiting to be tested at:

  http://httpd.apache.org/dev/dist/ 

Please report back with any problems.

Thanks for testing!


Sander


Re: 2.1.4 available for testing

2005-03-16 Thread William A. Rowe, Jr.
+/- 0 for alpha based on apr-iconv 1.1.0

Revisiting issues for apr-iconv 1.1.1 - if that's our prerequisite,
then I'm likely to lean +1.

At 03:00 PM 3/16/2005, Sander Striker wrote:
Hi all,

There are some 2.1.4-alpha tarballs waiting to be tested at:

 http://httpd.apache.org/dev/dist/

Please report back with any problems.

Thanks for testing!


Sander



Re: Puzzling News

2005-03-16 Thread Rasmus Lerdorf
William A. Rowe, Jr. wrote:
For anyone who wants to argue that this is a PHP-caused anomaly, note also
http://www.securityspace.com/s_survey/data/man.200501/apachemods.html
-10% followed by +11% the following month:
http://www.securityspace.com/s_survey/data/man.200502/apachemods.html
Big swings like that are almost always artificial.  One or two big 
domain parkers switching versions or toggling the server header.  You 
can't deduce much from that.

-Rasmus


Re: Puzzling News

2005-03-16 Thread William A. Rowe, Jr.
At 07:42 PM 3/16/2005, Rasmus Lerdorf wrote:
William A. Rowe, Jr. wrote:
For anyone who wants to argue that this is a PHP-caused anomaly, note also
http://www.securityspace.com/s_survey/data/man.200501/apachemods.html

-10% followed by +11% the following month:

http://www.securityspace.com/s_survey/data/man.200502/apachemods.html

Big swings like that are almost always artificial.  One or two big domain 
parkers switching versions or toggling the server header.  You can't deduce 
much from that.

Agreed.  February reports that both 1.3.33 and 2.0.53 are proving
sufficiently stable, ~90% push forward, ~10% fall back.  Of course
some users will encounter trouble and fall back to regroup.  Some
number less than 1 in 10 reassures me that the httpd project mostly
is moving forward.

I never look at the overall numbers, or number of adopters of any
given module.  Only looking for trends against the exact latest 
release we've shipped.



[STATUS] (httpd-2.0) Wed Mar 16 23:46:03 2005

2005-03-16 Thread Rodent of Unusual Size
APACHE 2.0 STATUS:  -*-text-*-
Last modified at [$Date: 2005-03-01 05:02:06 -0500 (Tue, 01 Mar 2005) $]

The current version of this file can be found at:
http://svn.apache.org/repos/asf/httpd/httpd/branches/2.0.x/STATUS

Release history:

2.0.54  : in development
2.0.53  : released February 7, 2005 as GA.
2.0.52  : released September 28, 2004 as GA.
2.0.51  : released September 15, 2004 as GA.
2.0.50  : released June 30, 2004 as GA.
2.0.49  : released March 19, 2004 as GA.
2.0.48  : released October 29, 2003 as GA.
2.0.47  : released July 09, 2003 as GA.
2.0.46  : released May 28, 2003 as GA.
2.0.45  : released April 1, 2003 as GA.
2.0.44  : released January 20, 2003 as GA.
2.0.43  : released October 3, 2002 as GA.
2.0.42  : released September 24, 2002 as GA.
2.0.41  : rolled September 16, 2002.  not released.
2.0.40  : released August 9, 2002 as GA.
2.0.39  : released June 17, 2002 as GA.
2.0.38  : rolled June 16, 2002.  not released.
2.0.37  : rolled June 11, 2002.  not released.
2.0.36  : released May 6, 2002 as GA.
2.0.35  : released April 5, 2002 as GA.
2.0.34  : tagged March 26, 2002.
2.0.33  : tagged March 6, 2002.  not released.
2.0.32  : released Feburary 16, 2002 as beta.
2.0.31  : rolled Feburary 1, 2002.  not released.
2.0.30  : tagged January 8, 2002.  not rolled.
2.0.29  : tagged November 27, 2001.  not rolled.
2.0.28  : released November 13, 2001 as beta.
2.0.27  : rolled November 6, 2001
2.0.26  : tagged October 16, 2001.  not rolled.
2.0.25  : rolled August 29, 2001
2.0.24  : rolled August 18, 2001
2.0.23  : rolled August 9, 2001
2.0.22  : rolled July 29, 2001
2.0.21  : rolled July 20, 2001
2.0.20  : rolled July 8, 2001
2.0.19  : rolled June 27, 2001
2.0.18  : rolled May 18, 2001
2.0.17  : rolled April 17, 2001
2.0.16  : rolled April 4, 2001
2.0.15  : rolled March 21, 2001
2.0.14  : rolled March 7, 2001
2.0a9   : released December 12, 2000
2.0a8   : released November 20, 2000
2.0a7   : released October 8, 2000
2.0a6   : released August 18, 2000
2.0a5   : released August 4, 2000
2.0a4   : released June 7, 2000
2.0a3   : released April 28, 2000
2.0a2   : released March 31, 2000
2.0a1   : released March 10, 2000

Please consult the following STATUS files for information on related projects:

* http://svn.apache.org/repos/asf/apr/apr/branches/0.9.x/STATUS
* http://svn.apache.org/repos/asf/apr/apr-util/branches/0.9.x/STATUS
* http://svn.apache.org/repos/asf/httpd/httpd/branches/2.0.x/docs/STATUS

Contributors looking for a mission:

* Just do an egrep on TODO or XXX in the source.

* Review the bug database at: http://issues.apache.org/bugzilla/

* Review the PatchAvailable bugs in the bug database:

  
http://issues.apache.org/bugzilla/buglist.cgi?bug_status=NEWbug_status=ASSIGNEDbug_status=REOPENEDproduct=Apache+httpd-2.0keywords=PatchAvailable

  After testing, you can append a comment saying Reviewed and tested.

* Open bugs in the bug database.

CURRENT RELEASE NOTES:

* Forward binary compatibility is expected of Apache 2.0.x releases, such
  that no MMN major number changes will occur.  Such changes can only be
  made in the trunk.

* All commits to branches/2.0.x must be reflected in SVN trunk,
  as well, if they apply.  Logical progression is commit to trunk,
  get feedback and votes in STATUS, and then merge into branches/2.0.x.

RELEASE SHOWSTOPPERS:

PATCHES TO BACKPORT FROM TRUNK:
  [ please place SVN revisions from trunk here, so it is easy to
identify exactly what the proposed changes are! ]
  [ please append new backports at the end of this list not the top. ]

*) mod_ssl: Set r-user from SSLUsername earlier so that it's
   actually useful.
   http://svn.apache.org/viewcvs.cgi?rev=153280view=rev
   http://svn.apache.org/viewcvs.cgi?rev=151493view=rev
   a.k.a. http://www.apache.org/~jorton/ap_ssluser.diff
   PR: 31418
   jerenkrantz comments: 151493 deletes a chunk and adds a chunk,
  with 153280 moving that added hunk elsewhere.  My brain hurts.
   +1: jorton, jerenkrantz

*) Add a build script to create a solaris package.
   svn rev 124104
   +1: minfrin, trawick

*) Get some control chars out of ap_log_error() invocations.
   Patch from Eric Covener with tweak by trawick:
   http://httpd.apache.org/~trawick/covener-removecontrolchars-2.0.patch
   (2.1-dev already has these fixes)
   +1: trawick, jorton

*) util_ldap: Add the directive LDAPConnectionTimeout to control
   the socket timeout value when binding to an LDAP server
   svn rev 126565
   +1: bnicholes, trawick (no need for APLOG_NOERRNO in Apache =2)

*) mod_ssl: fix to access mod_ssl-specific X509_STORE_CTX userdata
   

[STATUS] (httpd-2.1) Wed Mar 16 23:46:20 2005

2005-03-16 Thread Rodent of Unusual Size
APACHE 2.1 STATUS:  -*-text-*-
Last modified at [$Date: 2005-03-16 12:05:29 -0500 (Wed, 16 Mar 2005) $]

The current version of this file can be found at:
http://svn.apache.org/repos/asf/httpd/httpd/trunk/STATUS

Release history:
[NOTE that only Alpha/Beta releases occur in 2.1 development]

2.1.4   : in development
2.1.3   : Released on  2/22/2005 as alpha.
2.1.2   : Released on 12/08/2004 as alpha.
2.1.1   : Released on 11/19/2004 as alpha.
2.1.0   : not released.

Please consult the following STATUS files for information on related projects:

* http://svn.apache.org/repos/asf/apr/apr/trunk/STATUS
* http://svn.apache.org/repos/asf/apr/apr-util/trunk/STATUS
* http://svn.apache.org/repos/asf/httpd/httpd/trunk/docs/STATUS

Contributors looking for a mission:

* Just do an egrep on TODO or XXX in the source.

* Review the bug database at: http://issues.apache.org/bugzilla/

* Review the PatchAvailable bugs in the bug database:

  
http://issues.apache.org/bugzilla/buglist.cgi?bug_status=NEWbug_status=ASSIGNEDbug_status=REOPENEDproduct=Apache+httpd-2.0keywords=PatchAvailable

  After testing, you can append a comment saying Reviewed and tested.

* Open bugs in the bug database.

CURRENT RELEASE NOTES:

RELEASE SHOWSTOPPERS:

* Handling of non-trailing / config by non-default handler is broken
  http://marc.theaimsgroup.com/?l=apache-httpd-devm=105451701628081w=2
  jerenkrantz asks: Why should this block a release?

* the edge connection filter cannot be removed 
  http://marc.theaimsgroup.com/?l=apache-httpd-devm=105366252619530w=2
  jerenkrantz asks: Why should this block a release?
  stas replies: because it requires a rewrite of the filters stack
implementation (you have suggested that) and once 2.2 is
released you can't do that anymore. 

CURRENT VOTES:

* httpd-std.conf and friends

  a) httpd-std.conf should be tailored by install (from src or
 binbuild) even if user has existing httpd.conf
 +1:   trawick, slive, gregames, ianh, Ken, wrowe, jwoolley, jim, nd,
   erikabele
   wrowe - prefer httpd.default.conf to avoid ambiguity with cvs

  b) tailored httpd-std.conf should be copied by install to
 sysconfdir/examples
 -0:   striker

  c) tailored httpd-std.conf should be installed to
 sysconfdir/examples or manualdir/exampleconf/
 +1:   slive, trawick, Ken, nd (prefer the latter), erikabele

  d) Installing a set of default config files when upgrading a server
 doesn't make ANY sense at all.
 +1:   ianh - medium/big sites don't use 'standard config' anyway, as it
  usually needs major customizations
 -1:   Ken, wrowe, jwoolley, jim, nd, erikabele
   wrowe - diff is wonderful when comparing old/new default configs,
   even for customized sites that ianh mentions
   jim - ... assuming that the default configs have been updated
 with the required inline docs to explain the
 changes

* If the parent process dies, should the remaining child processes
  gracefully self-terminate. Or maybe we should make it a runtime
  option, or have a concept of 2 parent processes (one being a 
  hot spare).
  See: Message-ID: [EMAIL PROTECTED]

  Self-destruct: Ken, Martin, Lars
  Not self-destruct: BrianP, Ian, Cliff, BillS
  Make it runtime configurable: Aaron, jim, Justin, wrowe, rederpj, nd

  /* The below was a concept on *how* to handle the problem */
  Have 2 parents: +1: jim
  -1: Justin, wrowe, rederpj, nd
  +0: Lars, Martin (while standing by, could it do
something useful?)

* Make the worker MPM the default MPM for threaded Unix boxes.
  +1:   Justin, Ian, Cliff, BillS, striker, wrowe, nd
  +0:   BrianP, Aaron (mutex contention is looking better with the
latest code, let's continue tuning and testing), rederpj, jim
  -0:   Lars

  pquerna: Do we want to change this for 2.2?

RELEASE NON-SHOWSTOPPERS BUT WOULD BE REAL NICE TO WRAP THESE UP:

* Patches submitted to the bug database:
  
http://issues.apache.org/bugzilla/buglist.cgi?bug_status=NEWbug_status=ASSIGNEDbug_status=REOPENEDproduct=Apache+httpd-2.0keywords=PatchAvailable

* The Event MPM does not work on Solaris 10. PR 34040.

* Filter stacks and subrequests, redirects and fast redirects.
  There's at least one PR that suffers from the current unclean behaviour
  (which lets the server send garbage): PR 17629
  nd says: Every subrequest should get its own filter stack with the
   subreq_core filter as bottom-most. That filter does two things:
 - swallow EOS buckets
 - redirect the 

Re: 2.1.4 available for testing

2005-03-16 Thread Oden Eriksson
onsdag 16 mars 2005 22.00 skrev Sander Striker:
 Hi all,

 There are some 2.1.4-alpha tarballs waiting to be tested at:

   http://httpd.apache.org/dev/dist/

 Please report back with any problems.

 Thanks for testing!


 Sander

Hmm..., I get:

Starting httpd21: httpd21: Syntax error on line 241 
of /etc/httpd21/conf/httpd21.conf: Cannot 
load /usr/lib64/apache21/mod_authnz_ldap.so into 
server: /usr/lib64/apache21/mod_authnz_ldap.so: undefined symbol: 
util_ldap_cache_getuserdn

This happens on Mandrakelinux 10.1 (x86_64) and Mandrakelinux 10.2 (i586)

-- 
Regards // Oden Eriksson


Re: 2.1.4 available for testing

2005-03-16 Thread Paul Querna
Oden Eriksson wrote:
onsdag 16 mars 2005 22.00 skrev Sander Striker:
Hi all,
There are some 2.1.4-alpha tarballs waiting to be tested at:
 http://httpd.apache.org/dev/dist/
Please report back with any problems.
Thanks for testing!
Sander

Hmm..., I get:
Starting httpd21: httpd21: Syntax error on line 241 
of /etc/httpd21/conf/httpd21.conf: Cannot 
load /usr/lib64/apache21/mod_authnz_ldap.so into 
server: /usr/lib64/apache21/mod_authnz_ldap.so: undefined symbol: 
util_ldap_cache_getuserdn

This happens on Mandrakelinux 10.1 (x86_64) and Mandrakelinux 10.2 (i586)
Change the load order in your httpd.conf.
move the LoadModule for mod_ldap to before mod_authnz_ldap.
-Paul


Re: 2.1.4 available for testing

2005-03-16 Thread Paul Querna
Paul Querna wrote:
Oden Eriksson wrote:
onsdag 16 mars 2005 22.00 skrev Sander Striker:
Hi all,
There are some 2.1.4-alpha tarballs waiting to be tested at:
 http://httpd.apache.org/dev/dist/
Please report back with any problems.
Thanks for testing!
Sander

Hmm..., I get:
Starting httpd21: httpd21: Syntax error on line 241 of 
/etc/httpd21/conf/httpd21.conf: Cannot load 
/usr/lib64/apache21/mod_authnz_ldap.so into server: 
/usr/lib64/apache21/mod_authnz_ldap.so: undefined symbol: 
util_ldap_cache_getuserdn

This happens on Mandrakelinux 10.1 (x86_64) and Mandrakelinux 10.2 (i586)
Change the load order in your httpd.conf.
move the LoadModule for mod_ldap to before mod_authnz_ldap.
For reference, this is also PR 33568
http://issues.apache.org/bugzilla/show_bug.cgi?id=33568


Re: 2.1.4 available for testing

2005-03-16 Thread Oden Eriksson
torsdag 17 mars 2005 06.52 skrev Paul Querna:
 Oden Eriksson wrote:
  onsdag 16 mars 2005 22.00 skrev Sander Striker:
 Hi all,
 
 There are some 2.1.4-alpha tarballs waiting to be tested at:
 
   http://httpd.apache.org/dev/dist/
 
 Please report back with any problems.
 
 Thanks for testing!
 
 
 Sander
 
  Hmm..., I get:
 
  Starting httpd21: httpd21: Syntax error on line 241
  of /etc/httpd21/conf/httpd21.conf: Cannot
  load /usr/lib64/apache21/mod_authnz_ldap.so into
  server: /usr/lib64/apache21/mod_authnz_ldap.so: undefined symbol:
  util_ldap_cache_getuserdn
 
  This happens on Mandrakelinux 10.1 (x86_64) and Mandrakelinux 10.2 (i586)

 Change the load order in your httpd.conf.
 move the LoadModule for mod_ldap to before mod_authnz_ldap.

Ahh! I thought that loading order was something from the past?

Well, it works now. Will try some more after I have gotten some sleep...

Thanks Paul.

-- 
Regards // Oden Eriksson