There is an option to treat 304 as successful requests, but it affects all reports.
http://analog.cx/docs/include.html#304
However, I suspect that your redirects are using 302, not 304. Counting 302 as a successful. request can lead to double counting. e.g.
"GET / HTTP/1.1" 0 302 "" "GET /index.html HTTP/1.1" 1024 200 "http://example.com//";
-- Jeremy Wadsack Seven Simple Machines
Jon Russell wrote:
Hi,
I'm trying to (mis)use the Internal Search Report to report on banner ad click throughs.
I have a URL on the site /cgi-bin/redirect which takes a URL and redirects to it, so I can log the number of click throughs.
If I look in the Redirect Report I get :
reqs file
1300 /cgi-bin/redirect?u=www.google.com
1100 /cgi-bin/redirect?u=www.microsoft.com
900 /cgi-bin/redirect?u=www.aol.com
I have configured the Internal Search report with :
INTSEARCHENGINE /cgi-bin/redirect u
However, the report is blank. I assume this is because the Status Code of the /cgi-bin/redirect page is a 304, which Analog won't count in the Internal Search Report ?
Is there any way of forcing it to treat 304 as a 200 for the Internal Search Report ?
Regards,
Jon. +------------------------------------------------------------------------ | TO UNSUBSCRIBE from this list: | http://lists.meer.net/mailman/listinfo/analog-help | | Usenet version: news://news.gmane.org/gmane.comp.web.analog.general | List archives: http://www.analog.cx/docs/mailing.html#listarchives +------------------------------------------------------------------------
+------------------------------------------------------------------------ | TO UNSUBSCRIBE from this list: | http://lists.meer.net/mailman/listinfo/analog-help | | Usenet version: news://news.gmane.org/gmane.comp.web.analog.general | List archives: http://www.analog.cx/docs/mailing.html#listarchives +------------------------------------------------------------------------
