>Safe in this context means that submitting GET or HEAD requests should not
>change the state of the server for future requests. IOW - they should
>not have 'side effects'.
Searches don't affect the state of the server, but it has been argued
by some on this list that searches can be unsafe for robot access.
>> The only reason POST is "safe" at the moment is that the bloody-minded and
>> clueless section of the robot community are too incompetent to work out
>> how to correctly handle POST. I'm pretty sure those morons would be doing
>> POST too if they could figure it out.
> And you are scarcely winning friends among the group of people
>*you* are asking favors from by insulting them.
Anyone offended by my comment above must be categorizing themselves
as either "bloody-minded" or "clueless"... the comment clearly refers to
them and not the majority of the robot community.
[irrelevant critique of my HTML deleted]
I started this reading this list thinking there were two types of
robot owner. The resonsibible type and the type going through the
learning process and moving towards responsibility as they learn the
ropes. I now see that there's a 3rd type.. those that know about
guidelines, exclusion protocols, and the problems that robots *might*
cause to servers, but they've chosen to attempt to bend the 'rules'
to serve their own purpose.
Talking to this 3rd group is pointless, and I'm going to resist any
further flame-bate from these people. Irresponsible actions from those
who *should* know better will continue to give the robot community a
bad name. I know some of you are doing a good job, it's a shame you have
to put up with the others.
rob