Re: t_cmp oddities

2004-04-13 Thread Stas Bekman
Geoffrey Young wrote: I understand that your patch proposes to introduce: use Apache::TestUtil qw(:testmore); use Test::More; correct? Apache::Test, not TestUtil, but yes. argh, right, which makes my second part of the answer mostly irrelevant since I thought you were talking about TestUtil.

Re: error during make all

2004-04-13 Thread Aaron Bannert
You shouldn't have to run buildconf. Start from a clean tarball again and just run ./configure with your args and then make. -aaron On Apr 4, 2004, at 9:41 PM, Navneetha wrote: am am new to apache flood.i have downloaded the copy of flood .after successful download i am able to successfully

Re: Apache 1.3.30 release candidate tarball available for testing

2004-04-13 Thread Kean Johnston
Jim Jagielski wrote: At: http://httpd.apache.org/dev/dist/ Works great on SCO OpenServer 5.0.7 and UnixWare 7.1.3. Kean

Re: cvs commit: httpd-2.0/modules/experimental util_ldap.c

2004-04-13 Thread Jeff Trawick
[EMAIL PROTECTED] wrote: bnicholes2004/03/31 14:56:08 Modified:modules/experimental util_ldap.c Log: Update the DN information associated with each LDAP connection after util_ldap_cache_checkuserid() rebinds the connection. Revision ChangesPath 1.22 +12 -0

Re: Apache 1.3.30 release candidate tarball available for testing

2004-04-13 Thread David McCreedy
Tests out OK on IBM's TPF platform. -David Jim Jagielski [EMAIL PROTECTED]

1.3.3x digest/nonce issue

2004-04-13 Thread Jim Jagielski
There is a known bug/issue in the current implementation of mod_digest regarding the nonce. I am looking to have this plugged for our next 1.3 release. There are 2 suggested patches, which I will post under separate Emails. I will also adjust STATUS to reflect these 2 potential patches. PLEASE

[PATCH] Candidate 1: Re: 1.3.3x digest/nonce issue

2004-04-13 Thread Jim Jagielski
On Apr 13, 2004, at 11:13 AM, Jim Jagielski wrote: There is a known bug/issue in the current implementation of mod_digest regarding the nonce. I am looking to have this plugged for our next 1.3 release. There are 2 suggested patches, which I will post under separate Emails. I will also adjust

[PATCH] Candidate 2: Re: 1.3.3x digest/nonce issue

2004-04-13 Thread Jim Jagielski
On Apr 13, 2004, at 11:13 AM, Jim Jagielski wrote: There is a known bug/issue in the current implementation of mod_digest regarding the nonce. I am looking to have this plugged for our next 1.3 release. There are 2 suggested patches, which I will post under separate Emails. I will also adjust

RE: mod_cgi and apr_setup_signal_thread

2004-04-13 Thread Mathihalli, Madhusudan
You're partially correct. Here's whatz happening: worker.c: child_main() invokes apr_setup_signal_thread() signals.c: apr_setup_signal_thread() - sigfillset(sig_mask); remove_sync_sigs(sig_mask); sigprocmask(SIG_SETMASK, sig_mask, NULL) -

Re: [PATCH] Candidate 1: Re: 1.3.3x digest/nonce issue

2004-04-13 Thread Jeff Trawick
Jim Jagielski wrote: On Apr 13, 2004, at 11:13 AM, Jim Jagielski wrote: There is a known bug/issue in the current implementation of mod_digest regarding the nonce. I am looking to have this plugged for our next 1.3 release. There are 2 suggested patches, which I will post under separate Emails. I

Re: [PATCH] Candidate 1: Re: 1.3.3x digest/nonce issue

2004-04-13 Thread Jim Jagielski
Jeff Trawick wrote: Candidate patch #1: This was my patch to an earlier patch to address some build issues and point out a run-time problem with a sprintf call I guess I need to go through patch 2 and verify that everything was addressed, and/or point out the missing pieces (after I

Re: cvs commit: httpd-2.0/modules/experimental util_ldap.c

2004-04-13 Thread Brad Nicholes
You are correct although it isn't as bad as it seems. There are actually two types of caching going on here. There is the ldap connection cache and the user credential cache. Because the user credentials are cached, subsequent requests from the same user are not actually authenticated

Re: [PATCH] Candidate 1: Re: 1.3.3x digest/nonce issue

2004-04-13 Thread Ben Laurie
Jim Jagielski wrote: On Apr 13, 2004, at 11:13 AM, Jim Jagielski wrote: static const char *set_bs2000_account(cmd_parms *cmd, void *dummy, char *name) { @@ -3395,6 +3446,9 @@ An HTTP authorization type (e.g., \Basic\) }, { AuthName, set_authname, NULL, OR_AUTHCFG, TAKE1, The

Re: [PATCH] Candidate 1: Re: 1.3.3x digest/nonce issue

2004-04-13 Thread Joshua Slive
I do have one question about this: Is anyone actually using mod_digest? I was under the impression that there doesn't exist any client that can interoperate with this module (as opposed to mod_auth_digest, which supports modern clients). If this is true, why don't we just delete the darn thing?

Re: [PATCH] Candidate 1: Re: 1.3.3x digest/nonce issue

2004-04-13 Thread Geoffrey Young
Joshua Slive wrote: I do have one question about this: Is anyone actually using mod_digest? I was under the impression that there doesn't exist any client that can interoperate with this module (as opposed to mod_auth_digest, which supports modern clients). If this is true, why don't we

mod_ext_filter and last-modified header

2004-04-13 Thread Craig Sebenik
It looks like mod_ext_filter sets the last-modified http header based on the mod time of the *filter* file and not the actual file represented by the URL. eg. the following filter is configured in httpd.conf ExtFilterDefine filter-name mode=output intype=text/html outtype=text/html \

Re: mod_ext_filter and last-modified header

2004-04-13 Thread Geoffrey Young
Craig Sebenik wrote: It looks like mod_ext_filter sets the last-modified http header based on the mod time of the *filter* file and not the actual file represented by the URL. the Last-Modified HTTP header seems to be set based on the timestamp on /web_home/filters/filter.pl and NOT on

Re: mod_ext_filter and last-modified header

2004-04-13 Thread Craig Sebenik
Quoting Geoffrey Young ([EMAIL PROTECTED]): Craig Sebenik wrote: It looks like mod_ext_filter sets the last-modified http header based on the mod time of the *filter* file and not the actual file represented by the URL. the Last-Modified HTTP header seems to be set based on the