RSS IP Blocking

Nick Bradbury brought up the problem of RSS readers that are checking in too often and using up valuable bandwidth. So here is my clever idea that I don’t know how to implement just yet. RSS feeds are almost all dynamically generated (who would code that by hand with every update?). If you know the IPs that are causing problems you should be able to append a notice to only those feeds that politely tells them that they are checking for updates too often, why it is a problem, and how to correct it. In many cases this may just be a case of people not understanding that there is a problem at all or how to fix it.

Kevin Hall
Latest posts by Kevin Hall (see all)

5 thoughts on “RSS IP Blocking

  1. Yes but that creates more bandwidth consumption by appending a message to the posts. Slashdot actually does return a valid RSS feed when you get banned that says you have been banned.

    If RSS readers supported cookies (I’m not sure if they do or not), that could overcome the proxy problem.

  2. I like where you’re going with the cookies idea. That could help. But my concern is that banning users can alienate them. Part of the solution to such a problem should involve education and should engage them as a partner in solving the problem rather than as a problem user that must be banned. I think that most of the cases of badly configured RSS readers are innocent mistakes that result from a lack of knowledge.

    Additionally, one would hope that the additional message would result in the problem being fixed and the temporary increase in bandwidth to send it would result in a longer term reduction as the RSS readers are reconfigured. If the message is sent out with no results a certain number of times then the user could be banned.

  3. I’m not sure you can help me but I sure would like it if you could. It seems a few of my websites are linking to other IP’s. It’s as if the orginal IP is being “hijacked”. Any suggestions.


  4. Guy,
    I’m not an expert on hosting problems and this sounds like it is one. But my guess is that there is either some very good hacker screwing with you or someone has made a bad mistake at your hosting or wherever you have your domain names registered.
    I’d contact whoever you are going through to manage your Domain Name Servers (DNS) to make sure they don’t have any security holes and that they didn’t screw up your DNS while changing something else. Sometimes it is just a glitch in the system and the fix takes two minutes. Let me know how it that goes and if your hosting company or domain registrar can’t help we’ll see if we can figure something else out.

Comments are closed.