thanks,
- Patrick
On Aug 30, 2004, at 11:48 AM, Duke Hillard wrote:
I previously encountered a similar situation. My solution was to include a server redirect in my server's config file. The redirect brought visitors to the correct page and the resulting log entries were parsed by Analog in a manner that satisfied me.
HTH,
-- Duke
Patrick Robinson wrote:
Is there a way to restrict what gets included in the Directory Report, by HTTP status code? That is, requests that result in a "206 Partial Content" get included, but I want to exclude them.
Rationale:
I'm regularly seeing requests for URLs that look like this:
/pubs/<b>food</b>s/348-907/348-907.html
I don't know why, but some engine or other is putting <b></b> tags around portions of an otherwise valid URL. And my server often responds with a 206. These end up appearing in my Directory Report, and I'd rather they not.
Thanks!
-- Patrick Robinson AHNR Info Technology, Virginia Tech [EMAIL PROTECTED]
+------------------------------------------------------------------------ | TO UNSUBSCRIBE from this list: | http://lists.isite.net/listgate/analog-help/unsubscribe.html | | Digest version: http://lists.isite.net/listgate/analog-help-digest/ | Usenet version: news://news.gmane.org/gmane.comp.web.analog.general | List archives: http://www.analog.cx/docs/mailing.html#listarchives +------------------------------------------------------------------------
