I've solved the problem by doing it a different way:
CustomLog logs/my_log common "expr=%{QUERY_STRING} !~
/username.*password|password.*username/
On Thu, Aug 1, 2019 at 9:47 AM Ori Liel wrote:
>
>
> On Mon, Jul 29, 2019 at 3:13 PM Eric Covener wrote:
>
>> On Mon, Jul 29, 2019 at 7:56 AM Or
On Mon, Jul 29, 2019 at 3:13 PM Eric Covener wrote:
> On Mon, Jul 29, 2019 at 7:56 AM Ori Liel wrote:
> >
> > I have a server application, and for security reasons I'm trying to
> prevent requests, which provide 'username' and 'password' as query
> parameters, from being logged (providing these
On Mon, Jul 29, 2019 at 7:56 AM Ori Liel wrote:
>
> I have a server application, and for security reasons I'm trying to prevent
> requests, which provide 'username' and 'password' as query parameters, from
> being logged (providing these parameters as query parameters is a user
> mistake, but s
I have a server application, and for security reasons I'm trying to prevent
requests, which provide 'username' and 'password' as query parameters, from
being logged (providing these parameters as query parameters is a user
mistake, but still...)
I've tried this way:
* SetEnvIf QUERY_STRING
