We wish to give identified robots a 303 when they misbehave.
I would like to see this 303 in the status report but not count it as a
hit, like we do not count the 304's on static images as hits.
Can you please assist me in finding the best combo of includes and such
to let this happen?
Thanks
Here is the documentation in question
----
The STATUSINCLUDE and STATUSEXCLUDE commands are slightly different from
the rest. They work on HTTP status codes. (These codes are defined in
the HTTP spec, and viewable in the Status Code Report. But if you don't
already know about them, you really don't want to use these commands
anyway!) The arguments to the commands are a comma-separated list of
ranges. One end of the range can be blank, meaning from the first, or
to the last, status code. For example
STATUSINCLUDE 200-206,304,500-
would mean only look at lines with status codes 200-206, 304 or 500-599.
Some people want to exclude status code 304 (Not Modified) to stop those
requests appearing in the Request Report. But there is a better
solution. By default, analog counts code 304 as a successful request,
because it assumes that the cached version of the document is then
presented to the user. But you can count it as a redirected request
with the command
304ISSUCCESS OFF
For most people this is the wrong option, because code 304 is really the
same as code 200 to the user. So again, if you don't understand this,
stick with the default.
----
10.3.4 303 See Other
The response to the request can be found under a different URI and
SHOULD be retrieved using a GET method on that resource. This method
exists primarily to allow the output of a POST-activated script to
redirect the user agent to a selected resource. The new URI is not a
substitute reference for the originally requested resource. The 303
response MUST NOT be cached, but the response to the second
(redirected) request might be cacheable.
The different URI SHOULD be given by the Location field in the response.
Unless the request method was HEAD, the entity of the response SHOULD
contain a short hypertext note with a hyperlink to the new URI(s).
Note: Many pre-HTTP/1.1 user agents do not understand the 303
status. When interoperability with such clients is a concern, the
302 status code may be used instead, since most user agents react
to a 302 response as described here for 303.
+------------------------------------------------------------------------
| TO UNSUBSCRIBE from this list:
| http://lists.meer.net/mailman/listinfo/analog-help
|
| Analog Documentation: http://analog.cx/docs/Readme.html
| List archives: http://www.analog.cx/docs/mailing.html#listarchives
| Usenet version: news://news.gmane.org/gmane.comp.web.analog.general
+------------------------------------------------------------------------
