[PATCH] 2.0->2.1

This patch changes a lot of 2.0 references to 2.1. It doesn't get them all. Not all should change, anyway. In particular, most references in "Apache 2.0" in the docs are unchanged, because that requires a more careful review than the changes I've made here. Before I commit this, will

Can't compile HEAD on Linux

I can't compile current HEAD of httpd-2.0 due to the compiler errors shown in http://www.sebastian-bergmann.de/stuff/apr-util.txt. -- Sebastian Bergmann http://sebastian-bergmann.de/ http://phpOpenTracker.de/ Did I help you? Consider a gift: http://wishlist.sebastian-be

Re: cvs commit: httpd-2.0/server .cvsignore Makefile.in

On Fri, 6 Dec 2002 22:06:11 -0800, Wilfredo Sánchez wrote: > Is this because expat is in a directory containing "apr" in the path? Quite possibly. > What does "apu-config --includes" output for you? Yeah, mine is: I did actually include this in my post: >> My apu-config --include prints:

Re: [PATCH] Allowing extended characters in LDAP authentication...

At 03:42 PM 12/6/2002, Brad Nicholes wrote: >This patch adds a new directive "AuthLDAPConvertFromLanguage" to mod_auth_ldap >that allows the admin to either define a specific language when converting the user >ID to UTF8 of try to derive the language from the header. Ewww... charsets aren't

Re: cvs commit: httpd-2.0/server .cvsignore Makefile.in

Is this because expat is in a directory containing "apr" in the path? What does "apu-config --includes" output for you? Yeah, mine is: -I/usr/local/apache/include/apr-0 -I/usr/local/BerkeleyDB.4.1/include -I/usr/local/include because I build expat separately and put it in /usr/local.

Tagged the tree...

Hi, I tagged the 2.0 tree just yet as STRIKER_2_0_44_PRE1 in an attempt to get the 2.0.44 show on the road. Please test and point out any problems. This tag builds for me and serves pages at the minimum. I'll run the testsuite tomorrow. Sander PS. I forgot to commit Brian Havards patch befor

Re: [PATCH] Allowing extended characters in LDAP authentication...

I'm not very LDAP experienced, but nevertheless I see some problems: * Brad Nicholes wrote: > Attached is the first attempt at allowing user ID's with extended characters > as a valid login ID. Some browsers cannot use non-ascii characters (they cut as the first occurence). But that's probably

[PATCH] Allowing extended characters in LDAP authentication...

Attached is the first attempt at allowing user ID's with extended characters as a valid login ID. There are still problems with allowing extended characters in passwords because of the encryption methods used when assigning a user password in the directory. So far this appears to work when

Re: mod_usertrack patch

Jim, Resubmitting the patch, as you requested. -- Andrei Zmievski Mail: [EMAIL PROTECTED] Sr. Front End Software Engineer Web:http://www.fast.no/ Fast Search & Transfer Inc Phone: 781-304-2493 93 Worcester Street Fax:781-304-2410 Wellesley MA 02481-918

Re: mod_usertrack patch

Thanks! I'll look over during the weekend! At 9:16 AM -0500 12/6/02, Andrei Zmievski wrote: >Jim, > >Resubmitting the patch, as you requested. > >-- >Andrei Zmievski Mail: [EMAIL PROTECTED] >Sr. Front End Software Engineer Web:http://www.fast.no/ >Fast Search & Transfer Inc