You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@httpd.apache.org by Brian Munroe <br...@gmail.com> on 2007/08/21 01:09:52 UTC
[users@httpd] Conditional Logging for HTTP Status Codes
Just wanted to make sure I was reading the httpd documentation
correctly. There is no way to use conditional logging to drop 304
HTTP status codes, right?
Anyone have a solution they'd like to share?
thanks
-- brian
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Conditional Logging for HTTP Status Codes
Posted by Brian Munroe <br...@gmail.com>.
On 9/1/07, Matus UHLAR - fantomas <uh...@fantomas.sk> wrote:
>
> what's the point? 304 is understood as a hit, the same as 200, but the
> content is not resent to client, because client already has it.
>
Just trying to reduce the size of access.logs. It isn't a big deal,
but I just thought that it was weird that Apache didn't provide the
ability to filter on status code, and thought maybe I was reading the
documentation wrong.
-- brian
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Conditional Logging for HTTP Status Codes
Posted by Matus UHLAR - fantomas <uh...@fantomas.sk>.
> On 8/20/07, Vincent Bray <no...@gmail.com> wrote:
> > And further, it's probably not worth it to do so as you can just
> > filter the logs during processing, or during the logging by using a
> > piped logger.
On 21.08.07 11:02, Brian Munroe wrote:
> That is the solution I am looking into. Thanks for the confirmation.
what's the point? 304 is understood as a hit, the same as 200, but the
content is not resent to client, because client already has it.
--
Matus UHLAR - fantomas, uhlar@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Despite the cost of living, have you noticed how popular it remains?
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Conditional Logging for HTTP Status Codes
Posted by Brian Munroe <br...@gmail.com>.
On 8/20/07, Vincent Bray <no...@gmail.com> wrote:
>
> And further, it's probably not worth it to do so as you can just
> filter the logs during processing, or during the logging by using a
> piped logger.
>
That is the solution I am looking into. Thanks for the confirmation.
-- brian
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Conditional Logging for HTTP Status Codes
Posted by Vincent Bray <no...@gmail.com>.
On 21/08/07, Vincent Bray <no...@gmail.com> wrote:
> On 21/08/07, Brian Munroe <br...@gmail.com> wrote:
> > Just wanted to make sure I was reading the httpd documentation
> > correctly. There is no way to use conditional logging to drop 304
> > HTTP status codes, right?
> >
> > Anyone have a solution they'd like to share?
>
> I can't think of one. I'd like to be corrected, but I'm not aware of
> any way to conditionally do anything based on the status code of a
> non-error response. You'd need to either hack up mod_log_config or add
> your own module.
And further, it's probably not worth it to do so as you can just
filter the logs during processing, or during the logging by using a
piped logger.
--
noodl
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Conditional Logging for HTTP Status Codes
Posted by Vincent Bray <no...@gmail.com>.
On 21/08/07, Brian Munroe <br...@gmail.com> wrote:
> Just wanted to make sure I was reading the httpd documentation
> correctly. There is no way to use conditional logging to drop 304
> HTTP status codes, right?
>
> Anyone have a solution they'd like to share?
I can't think of one. I'd like to be corrected, but I'm not aware of
any way to conditionally do anything based on the status code of a
non-error response. You'd need to either hack up mod_log_config or add
your own module.
--
noodl
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org