On 9/5/06, William A. Rowe, Jr. <[EMAIL PROTECTED]> wrote:
Jeff Trawick wrote:
>> >
>> > AP_DECLARE(const char *) ap_get_server_banner() {
>> > return ap_get_server_version();
>> > }
I would prefer, if server_version goes away, and we want users to be
unsurprised, that it's
/* doxygen descr
Jeff Trawick wrote:
>> >
>> > AP_DECLARE(const char *) ap_get_server_banner() {
>> > return ap_get_server_version();
>> > }
I would prefer, if server_version goes away, and we want users to be
unsurprised, that it's
/* doxygen description...
* @deprecated @see ap_get_server_banner
*/
AP_DEC
Ruediger Pluem wrote:
>
> Hm, what backport are you thinking of? I thought of backporting it to 2.2.x
> not to 2.0.x. I see no general backwards compatibilty of modules written for
> 2.2.x to 2.0.x.
Well, we are talking about breaking <= 2.2.3 / > 2.2.3 right?
You are right, the new function wou
On 9/5/06, William A. Rowe, Jr. <[EMAIL PROTECTED]> wrote:
Brian Akins wrote:
> Ruediger Pluem wrote:
>
>> 1. If we stick to
>>
>> AP_DECLARE(const char *) ap_get_server_version(void);
>>
>> and do
>>
>> #define ap_get_server_banner ap_get_server_version
>
>
> I hate macros. Just do it like:
>
>
On 09/05/2006 11:49 PM, William A. Rowe, Jr. wrote:
> Brian Akins wrote:
>
>>Ruediger Pluem wrote:
>>
>>
>>>1. If we stick to
>>>
>>>AP_DECLARE(const char *) ap_get_server_version(void);
>>>
>>>and do
>>>
>>>#define ap_get_server_banner ap_get_server_version
>>
>>
>>I hate macros. Just do it li
Brian Akins wrote:
> Ruediger Pluem wrote:
>
>> 1. If we stick to
>>
>> AP_DECLARE(const char *) ap_get_server_version(void);
>>
>> and do
>>
>> #define ap_get_server_banner ap_get_server_version
>
>
> I hate macros. Just do it like:
>
> AP_DECLARE(const char *) ap_get_server_banner() {
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 05 Sep 2006 22:00:59 +0100 Jeff Trawick <[EMAIL PROTECTED]>
wrote:
>On 9/5/06, Ruediger Pluem <[EMAIL PROTECTED]> wrote:
>>
>>
>> On 09/05/2006 03:08 PM, wrote:
>> > Author: trawick
>> > Date: Tue Sep 5 06:08:15 2006
>> > New Revision: 44033
On 9/5/06, Ruediger Pluem <[EMAIL PROTECTED]> wrote:
On 09/05/2006 03:08 PM, wrote:
> Author: trawick
> Date: Tue Sep 5 06:08:15 2006
> New Revision: 440337
>
> URL: http://svn.apache.org/viewvc?view=rev&rev=440337
> Log:
> Replace ap_get_server_version with ap_get_server_banner() and
> ap_get
On Sep 5, 2006, at 11:49, Brad Nicholes wrote:
So it sounds like there are two questions being asked. First,
what non-ldap usages are there for authnAlias and second why
doesn't the configuration below work?
I'll answer the second question first. Given the configuration
block bel
Ruediger Pluem wrote:
1. If we stick to
AP_DECLARE(const char *) ap_get_server_version(void);
and do
#define ap_get_server_banner ap_get_server_version
I hate macros. Just do it like:
AP_DECLARE(const char *) ap_get_server_banner() {
return ap_get_server_version();
}
That way, i
On 09/05/2006 03:08 PM, wrote:
> Author: trawick
> Date: Tue Sep 5 06:08:15 2006
> New Revision: 440337
>
> URL: http://svn.apache.org/viewvc?view=rev&rev=440337
> Log:
> Replace ap_get_server_version with ap_get_server_banner() and
> ap_get_server_description().
>
> High-level summary:
>
> T
So it sounds like there are two questions being asked. First, what non-ldap
usages are there for authnAlias and second why doesn't the configuration below
work?
I'll answer the second question first. Given the configuration block below,
I don't know why it doesn't work. I just retest
Hi,
Line 2188 in proxy_util.c has:
if (APR_SUCCESS != apr_bucket_read(e, (const char **)&response,
&len, APR_BLOCK_READ)) {
return rv;
}
should this be:
if (APR_SUCCESS != (rv = apr_bucket_read(e, (const char
**)&response, &le
According to Swapan:
> Do I need any additional configuration specifically for TRACE methods?
You may want to consider updating your version of Apache and using
the TraceEnable option instead.
http://httpd.apache.org/docs/2.2/en/mod/core.html#traceenable
ciao...
--
Lars Eilebrecht
[EMAIL PR
Title: Apache - TRACE vulnerability solution
Hi,
I am using Apache 2.0.54 and trying out the suggested solution for the Http TRACE vulnerability as mentioned at https://www.kb.cert.org/vuls/id/867593
using the mod_rewrite module and specifying the following lines in .htaccess file.
Rewrite
On Sep 5, 2006, at 09:28, Jeff Trawick wrote:
On 8/20/06, Lars Eilebrecht <[EMAIL PROTECTED]> wrote:
According to William:
> My 2c, let's adopt the patch for three reasons...
>
> 1. it's an FAQ that would -go away-, less stress for our peer
apache
> user supporters
Is it really an FA
William A. Rowe, Jr. wrote:
Project Committee Members...
Adopt [EMAIL PROTECTED],
+1
seeded from [EMAIL PROTECTED] current subscribers,
-1
Bill
I just recompiled Apache 2.0.59, using the 0.9.7 apr(-util) which is the
version supplied with Apache 2.0.55.
This results in a working system. I can kill -9 an apache process and the
webserver will respond normally. The master process willl create a new
apache process.
I conclude that somewhere
On 8/20/06, Lars Eilebrecht <[EMAIL PROTECTED]> wrote:
According to William:
> My 2c, let's adopt the patch for three reasons...
>
> 1. it's an FAQ that would -go away-, less stress for our peer apache
> user supporters
Is it really an FAQ? Hmm ... the last time it was discussed on the dev
On 8/20/06, William A. Rowe, Jr. <[EMAIL PROTECTED]> wrote:
Lars Eilebrecht wrote:
>
> Apart from that, it's also possible to customize the Server header by
> using mod_security which has a configuration directive for this.
My 2c, let's adopt the patch for three reasons...
1. it's an FAQ that
This went first to users@, but it appears that the auth-fu isn't
strong there right now. ;-)
I was hoping that someone (Brad?) might be able to assist me with
this. I was trying to come up with a non-LDAP example for the
documentation, since this seems a really useful feature that should
21 matches
Mail list logo
