[EMAIL PROTECTED] wrote:
We shouldn't be returning 416 Invalid Range for something that's
redirected, but it sure looks like we are. I wonder what the byterange filter
does when it sees a redirect response, and there are input Range: headers?
To answer my own question, it's definately
check this out:
[gregamesdaedalus gregames]$ grep 194.65.14.76 .*binaries.* 416
/logs/www/weblog | wc -l
69763
I asked root to block this IP for a while, because we are getting a couple of
these every second. I suspect there's an httpd bug here as well as a looping
client. We shouldn't be
