We have a little application that pulls in feeds from FeedBurner that
uses SimplePie 1.0 Beta 2. Recently, some of the feeds our app reads
have stopped working, getting a 404 from FeedBurner. Since the feeds
still look fine in a browser, I guessed it had something to do with
the user agent.
So, I dug through the SimplePie code and found that it had this user
agent sting:
SimplePie/1.0 Beta 2 (Feed Parser; http://simplepie.org/; Allow like
Gecko) Build/20060530
I started messing around with it at that point and discovered that as
long as the string "simplepie" wasn't in the user agent string,
FeedBurner would respond correctly. But the instant s-i-m-p-l-e-p-i-e
appears, we get the 404. In other words:
> We have a little application that pulls in feeds from FeedBurner that
> uses SimplePie 1.0 Beta 2. Recently, some of the feeds our app reads
> have stopped working, getting a 404 from FeedBurner. Since the feeds
> still look fine in a browser, I guessed it had something to do with
> the user agent.
> So, I dug through the SimplePie code and found that it had this user
> agent sting:
> I started messing around with it at that point and discovered that as
> long as the string "simplepie" wasn't in the user agent string,
> FeedBurner would respond correctly. But the instant s-i-m-p-l-e-p-i-e
> appears, we get the 404. In other words:
Just got a message from the FeedBurner Operations Team. SimplePie
clients that do not have caching configured will be forwarded to the
secondary data-center of FeedBurner, which does not always have
immediately up-to-date content.
On Sep 9, 4:21 pm, Franklin Tse [Community Expert] wrote:
> Just got a message from the FeedBurner Operations Team. SimplePie
> clients that do not have caching configured will be forwarded to the
> secondary data-center of FeedBurner, which does not always have
> immediately up-to-date content.
How does FeedBurner tell if caching is enabled or not? Just by the
frequency of requests without either of the If-Modified-Since/If-None-
Match headers?
|
