on 07:45 Thu 10 Mar, Todd (slackmoehrle.lists@xxxxxxxxx) wrote:
> LogWatch reports items like:
>
> Connection attempts using mod_proxy:
> 83.167.123.83 -> 205.188.251.1:443: 1 Time(s)
> 83.167.123.83 -> 64.12.202.36:443: 2 Time(s)
>
> Requests with error response codes
> 403 Forbidden
> 205.188.251.1:443: 1 Time(s)
> 64.12.202.36:443: 2 Time(s)
> 404 Not Found
> //jmx-console/HtmlAdaptor: 1 Time(s)
> /VINT_1984_THINK_DIFFERENT: 1 Time(s)
> /mobo.png: 1 Time(s)
> /player.swf: 1 Time(s)
> /robots.txt: 4 Time(s)
>
> Now, I know mod_proxy is turned off by default, but is there a way to "play
> games" with those that attempt a proxy connection? Like a ReWrite rule or
> some sort?
>
> For the 404's, Obviously these don't exist, but robots.txt so I am not sure
> why that has a 404.
>
> What are 406 errors? Some Googling say they are due to mod_security issues
> and that an .htaccess fix can turn it off. But I don't understand the issue
> and the solution to be honest.
HTTP status codes generally:
http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
Slightly more user-friendly descriptive guide:
http://www.addedbytes.com/for-beginners/http-status-codes/
406 indicates an unacceptable request.
Bumping up your apache debug levels and watching the error log may help,
as could snooping the traffic generating the request (packet/GET
request).
--
Dr. Ed Morbius, Chief Scientist / |
Robot Wrangler / Staff Psychologist | When you seek unlimited power
Krell Power Systems Unlimited | Go to Krell!
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
