APACHE 2.1 STATUS: -*-text-*-
Last modified at [$Date: 2004/09/03 02:47:19 $]
Release [NOTE that only Alpha/Beta releases occur in 2.1 development]:
2.1.0 : in development
Please consult the following STATUS files for information
on related proj
APACHE 2.0 STATUS: -*-text-*-
Last modified at [$Date: 2004/11/03 22:16:54 $]
Release:
2.0.53 : in development
2.0.52 : released September 28, 2005 as GA.
2.0.51 : released September 15, 2004 as GA.
2.0.50 : released June 30, 2004 a
APACHE 1.3 STATUS: -*-text-*-
Last modified at [$Date: 2004/10/30 13:20:38 $]
Release:
1.3.34-dev: In development.
1.3.33: Tagged October 27, 2004
1.3.32: Tagged October 18, 2004. Not formally released.
1.3.31: Tagged May 7, 2004. Announc
Joe Orton wrote:
On Wed, Nov 03, 2004 at 01:39:20PM -0500, Bill Stoddard wrote:
Joe Orton wrote:
+/* Now NUL-terminate the string at the end of the line;
+ * if the last-but-one character is a CR, terminate there */
+if (last_char > *s && last_char[-1] == APR_ASCII_CR) {
last_char[-1]
You are correct that a patch based on mod_authnz_ldap.c won't apply
cleanly to mod_auth_ldap.c because of various differences in the code
base. But the patch is fairly self-contained meaning that the same
chunk of code can easily be copied from mod_authnz_ldap.c and pasted
into mod_auth_ldap.c w
On Wed, Nov 03, 2004 at 10:16:55PM -, [EMAIL PROTECTED] wrote:
...
> +*) mod_authnz_ldap: Added the directive "Requires ldap-attribute" that
> + allows the module to only authorize a user if the attribute value
> + specified matches the value of the user object. PR 31913
>
On Wed, Nov 03, 2004 at 01:39:20PM -0500, Bill Stoddard wrote:
> Joe Orton wrote:
>
> >+/* Now NUL-terminate the string at the end of the line;
> >+ * if the last-but-one character is a CR, terminate there */
> >+if (last_char > *s && last_char[-1] == APR_ASCII_CR) {
>
> last_char[-1
Jeff Trawick wrote:
At best, ap_sock_disable_nagle() is of limited use (just call
apr_socket_option_set and log if it fails), and at worst it hides
information (no retcode) and has no information to know
when/where/what to log. So yank it.
+1
Also:
Change httpd so that a connection-oriented nagle
Joe Orton wrote:
+/* Now NUL-terminate the string at the end of the line;
+ * if the last-but-one character is a CR, terminate there */
+if (last_char > *s && last_char[-1] == APR_ASCII_CR) {
last_char[-1]... yack, that's just nasty syntax if you ask me.
Bill
Brad Nicholes wrote:
>
>I like the suggestion as well because I think that would be the right
> way to implement complex LDAP expressions. But it would probably take
> adding at least a new util_ldap_filter_search() API to Util_ldap() in
> order to accomodate this functionality. The advantag
I like the suggestion as well because I think that would be the right
way to implement complex LDAP expressions. But it would probably take
adding at least a new util_ldap_filter_search() API to Util_ldap() in
order to accomodate this functionality. The advantage of also having an
ldap-attribu
Good suggestion. I am +1 for the patch as-is with the intent
of looking into adding the below
On Nov 3, 2004, at 5:04 AM, Graham Leggett wrote:
Brad Nicholes wrote:
I took a quick look at this patch and it seems to work well as long
as all of the listed attributes are OR'ed together. I don't ha
Brad Nicholes wrote:
I took a quick look at this patch and it seems to work well as long
as all of the listed attributes are OR'ed together. I don't have a good
suggestion yet, but is there a way to implement the logic so that
attributes could be also AND'ed together? Or even a NOT-EQUAL
opera
13 matches
Mail list logo
