auth headers & logging

[steven <st...@cotton.dk>]

Hi,

I'm rewriting authentication headers on the fly and those rewritten
headers are being logged, but I would like to log the details supplied by
the client as opposed to what I've rewritten them as. I thought of writing
a logging module and passing it a note, but it seems a bit long-winded and
I'm worried about the performance overhead. Is there a more efficient way
of doing this?

Thanks,

-- 
steven

Re: auth headers & logging

[steven <st...@cotton.dk>]

On Mon, 2 Oct 2000, Matthew Byng-Maddick wrote:

> Given that filling the notes table is the standard method for things to be
> logged, then is there much of a performance overhead. You might even be
> able to pass data using notes to the standard apache logging mechanism,
> although I'm not the right person to know quite how to do this.

Ok, after some extra reading I don't think it's going to be that bad. I
simply created a note and changed the LogFormat directive in my conf file
to log that in place of the authentication header.

Thanks,

-- 
steven

Re: auth headers & logging

[Matthew Byng-Maddick <mb...@colondot.net>]

On Mon, 2 Oct 2000, steven wrote:
> I'm rewriting authentication headers on the fly and those rewritten
> headers are being logged, but I would like to log the details supplied by
> the client as opposed to what I've rewritten them as. I thought of writing
> a logging module and passing it a note, but it seems a bit long-winded and
> I'm worried about the performance overhead. Is there a more efficient way
> of doing this?

Given that filling the notes table is the standard method for things to be
logged, then is there much of a performance overhead. You might even be
able to pass data using notes to the standard apache logging mechanism,
although I'm not the right person to know quite how to do this.

MBM

-- 
The power to destroy a planet is insignificant  when compared to the power
of the Force.                                               -- Darth Vader