Re: [users@httpd] Apache logging format

2016-01-28 Thread Jim Jagielski
The standard format strings for data to log can be found at: http://httpd.apache.org/docs/current/mod/mod_log_config.html#formats Is a 403 status code good enough for what you want regarding failure? > On Jan 28, 2016, at 12:38 PM, K R wrote: > > Is there a way to capture user login use

Re: [users@httpd] Apache logging format

2016-01-28 Thread K R
we are using SAML . On Thu, Jan 28, 2016 at 11:52 AM, Richard < lists-apa...@listmail.innovate.net> wrote: > > > > Date: Thursday, January 28, 2016 09:38:47 -0800 > > From: K R > > > > Is there a way to capture user login user login failure in > > Apache logs. > > > > TIA > > > What are you

Re: [users@httpd] Apache logging format

2016-01-28 Thread Richard
> Date: Thursday, January 28, 2016 09:38:47 -0800 > From: K R > > Is there a way to capture user login user login failure in > Apache logs. > > TIA What are you using for your authentication method/access control - http-basic, application-specific, something else? -

[users@httpd] Apache logging format

2016-01-28 Thread K R
Is there a way to capture user login user login failure in Apache logs. TIA

RE: [users@httpd] apache Logging output changed?

2005-06-21 Thread Noah
On Tue, 21 Jun 2005 15:14:16 +0200, Boyle Owen wrote > > -Original Message- > > From: Noah [mailto:[EMAIL PROTECTED] > > Sent: Dienstag, 21. Juni 2005 14:42 > > To: apache > > Subject: [EMAIL PROTECTED] apache Logging output changed? > > > > > > apache+mod_ssl-1.3.33+2.8.22 > > FreeBSD-4.

RE: [users@httpd] apache Logging output changed?

2005-06-21 Thread Boyle Owen
> -Original Message- > From: Noah [mailto:[EMAIL PROTECTED] > Sent: Dienstag, 21. Juni 2005 14:42 > To: apache > Subject: [EMAIL PROTECTED] apache Logging output changed? > > > apache+mod_ssl-1.3.33+2.8.22 > FreeBSD-4.11R3 > > This is really important for us to fix so I am asking again.

[users@httpd] apache Logging output changed?

2005-06-21 Thread Noah
apache+mod_ssl-1.3.33+2.8.22 FreeBSD-4.11R3 This is really important for us to fix so I am asking again. so I upgraded apache 1.3.33 from /usr/ports some about a month ago and around that time I stopped seeing POST log messages for my perl scripts ending up in my server's access logs. any clues

[users@httpd] apache Logging output changed?

2005-06-20 Thread Noah
apache+mod_ssl-1.3.33+2.8.22 FreeBSD-4.11R3 so I upgraded apache 1.3.33 from /usr/ports some about a month ago and around that time I stopped seeing POST log messages for my perl scripts ending up in my server's access logs. any clues why this is no longer being logged. is there some log granu

[users@httpd] apache Logging output changed?

2005-06-20 Thread Noah
apache+mod_ssl-1.3.33+2.8.22 FreeBSD-4.11R3 so I build apache 1.3.33 some about a month ago and around that time I stopped seeing POST log messages for my perl scripts ending up in my server's access logs. any clues why this is no longer being logged. is there some log granualrity configur

[users@httpd] Apache Logging!

2005-06-08 Thread RAJESH SEGU
Hello Guys! I have a small problem[not exactly], it might be very silly but cannot sleep without an idea. I want to log debug messages from the module into a different file other than error_log and access_log file to maintain and analyse my logs. Sinec I am using apache[multi threaded/multi proce