Somebody has been sending OPTION method requests to my Apache server - I've
since blocked them out with a limit directive, but I'd like to exclude the
ones I already have from my Analog reports.
The request in my log looks like:
"OPTIONS * HTTP/1.0"
This is showing up in my requests report as re
As you probably already know, Analog usually treats the asterisk (*) as
a wildcard. In this case, you want to treat the asterisk as a literal
string.
There are a couple of places in the documentation that mention "literals".
One of these is at "http://www.analog.cx/docs/alias.html"; and another i
At 03:41 PM 6/20/2003 -0500, Dukewrote:
As you probably already know, Analog usually treats the asterisk (*) as
a wildcard. In this case, you want to treat the asterisk as a literal string.
There are a couple of places in the documentation that mention "literals".
One of these is at "http://www.an
On Mon, 23 Jun 2003, Phil Glatz wrote:
>
> Thanks, Duke - unfortunately, this appears to only work for alias commands.
>
> I can't find a consistent syntax to escape literal characters for request
> commands.
>
Yes, PLAIN: only works on the right hand side of an alias. On the left hand
side you ca
At 10:14 AM 6/24/2003 +0100, you wrote:
> I can't find a consistent syntax to escape literal characters for request
> commands.
>
Yes, PLAIN: only works on the right hand side of an alias. On the left hand
side you can use regular expressions. Try
FILEEXCLUDE REGEXP:\*
(Actually, that will exclud
On Wed, 25 Jun 2003, Phil Glatz wrote:
>
> I'm trying to do something similar with referrer reports - shouldn't
>REFREPEXCLUDE REGEXPI:^.*foo.com.*$
>
> exclude any URL with foo.com in any place in it from referrer reports?
>
Well, yes, but you only need REGEXPI:foo.com
Actually, it's not qui
