How much of the traffic is “unnecessary”, though? That would be interesting to analyze, but it would take some knowledge of what UA‘s were pulling feeds, how often you were posting [thereby making a poll of your feed worthwhile], how often your server returned Not Modified HTTP Headers, etc.
WordPress RSS feeds support proper HTTP headers for communicating last modified times, and the vast majority of RSS clients support that. The only funky usage I noticed when browsing through things was 4 GB eaten by WGET a few days ago. Ouch.
Thanks to people like me 🙂
How much of the traffic is “unnecessary”, though? That would be interesting to analyze, but it would take some knowledge of what UA‘s were pulling feeds, how often you were posting [thereby making a poll of your feed worthwhile], how often your server returned Not Modified HTTP Headers, etc.
More work than I want …
WordPress RSS feeds support proper HTTP headers for communicating last modified times, and the vast majority of RSS clients support that. The only funky usage I noticed when browsing through things was 4 GB eaten by WGET a few days ago. Ouch.