is valid, then I will check
Request_URI and based on that I will log it. I understand that I
cannot check Request_URI for invalid requests. But why I cannot
disable logging of invalid requests? I would like to be able to
disable that in CustomLog and maybe just get a warning in error log,
something
On Sun, Dec 14, 2008 at 1:35 PM, Mitar wrote:
> And now I do not have invalid requests logged. I do not like that but
> I do not like having them logged even more. I really do not understand
> why this short-circuiting is necessary. We have an error log for such
> "important" things. CustomLog sh
Hi!
On Sun, Dec 14, 2008 at 3:46 PM, Morgan Gangwere <0.fracta...@gmail.com> wrote:
> Well, more accurately, this is kinda backwards. According to the
> "documentation", the syntax for SetEnvIf is
>
> SetEnvIf (statement) (statement) (varname)
In my documentation:
http://httpd.apache.org/docs/2.
Joshua Slive wrote:
On Thu, Dec 11, 2008 at 11:32 PM, Mitar wrote:
Hi!
Is there a way to disable logging of invalid requests to an HTTP
server (which result in a 501 response code)? I would like to log only
specific URLs and I am using SetEnvIf with CustomLog to do that, like:
SetEnvIf
On Thu, Dec 11, 2008 at 11:32 PM, Mitar wrote:
> Hi!
>
> Is there a way to disable logging of invalid requests to an HTTP
> server (which result in a 501 response code)? I would like to log only
> specific URLs and I am using SetEnvIf with CustomLog to do that, like:
>
>
Hi!
Is there a way to disable logging of invalid requests to an HTTP
server (which result in a 501 response code)? I would like to log only
specific URLs and I am using SetEnvIf with CustomLog to do that, like:
SetEnvIf Request_URI "^/$" log_request=yes
SetEnvIf Request_URI &qu
