[analog-help] FILEEXCLUDE via anlgform
Walter Ian Kaye
analog-help at natural-innovations.com
Sat Nov 24 07:37:33 PST 2007
At 06:22 p -0500 11/21/2007, Aengus didst inscribe upon an electronic papyrus:
>Walter Ian Kaye <analog-help at natural-innovations.com> wrote:
>> At 03:47 p +0000 11/21/2007, Hunter John didst inscribe upon an
>>
>> Hmm... maybe it didn't work because I didn't have root-relative paths?
>> I had *.gif -- does it only match from the "left"?
>
>*.gif should work just fine.
>
>Do a simple test from first principles - create a 4 line logfile
>with each entry having a different file type. Run analog against it
>with your current .cfg file, and see if your FILEEXCLUDEs work as
>expected.
Where is my .cfg file? I've never seen it....
>If they don't, then run analog against the test logfile without any .cfg file:
>
>analog test.log -G +C"FILEEXCLUDE *.gif" +OReport.html
>
>This will demonstrate how analog interprets the FILEEXCLUDE command.
OK, I tried that command line on my real log file, and added *.jpg
and *.swf to the exclusion. The gifs/jpegs were excluded, but the
.swf files still showed up. What is going on there? The .swf was
followed by a line for the .swf's query string for clickthru's
(highlighted in a different color). Is that a separate issue? Is the
line above only there to indicate the caller/referrer for the
clickthru?
>If you're still getting unexpected results, then the order of your
>INCLUDES/EXCLUDES is the problem. SETTINGS ON will show you the
>order in which they are being applied.
What sort of interaction is there between the anlgform.pl script and
any other settings elsewhere (wherever elsewhere is -- I haven't
touched anything else)?
thanks,
-W
More information about the analog-help
mailing list