Welcome to WebmasterWorld Guest from 22.214.171.124 , register , free tools , login , search , pro membership , help , library , announcements , recent posts , open posts Pubcon Platinum Sponsor 2014
Help interpreting this 406 teylyn
I notice a particular 406 error in my logs and find that it is always the same user agent Mozilla/4.0+(compatible;+Cerberian+Drtrs+Version-3.2-Build-0)
It comes, tries to grab a gif file and then disappears with a 406 status. The gif file is correctly named and it sits on the server and can be accessed allright. I have looked up the 406 status on [
...] but frankly, this explanation is way to technical for me. w3.org
Does someone want to enlighten me on what's happening here?
400 class error codes are client side. So the issue is not with the gif but with the request.
I believe Cerberian is a non-spidering monitoring agent...
Sorry if this is the wrong forum, but since it is in my logs and this forum is about tracking and logging I thought it was all right to ask a question to help me better understand my logs.
Thanks for taking the trouble to reply, but it would have been more helpful to me and other relatively new forum users to name the more appropriate forum.
I can only assume that since you identified the user agent as a spider, that means I should have been posting in the forum for search engine spider identification.
Thing is, I was not aware that it is a spider, and I was not clear on what the status 406 means.
Misunderstanding. Sorry about that....
The second message I posted was in the wrong forum. I was trying to reply to another post in a different forum. My mistake - not yours.
Check your sticky mail for more info on your original post.
Hey, that's all right! No offence taken. It's an accident waiting to happen for me too, trying to read several posts at once. That's what you get with multi-tabbed browsers.
OK - now deleting that post really WOULD be confusing Quinn, so I'll just leave it all where it is :)
oops, I deleted it, well I guees if I am not part of the solution ;)
the gist of a 406 is that it is a malformed request from the client side, as Quinn mentioned, I never worry about them