search

appdotnet / pourover

RSS publishing for App.net
35 stars 10 forks source link

Old feed data, no refresh possible #6

Open rretsiem opened 11 years ago

rretsiem commented 11 years ago

PourOver seems to pull old feed data from my PuSH enabled feed and stopped updating the feed.

The feed url: http://blog.renem.net/atom.xml

All other feed services work fine with this feed and get the information as soon as I ping the hub. Also a delete feed and re-add didn't helped here.

voidfiles commented 11 years ago

Well the feed looks to be subscribed to PuSH properly now, the old feed wasn't. The next time you publish something let me know and I will look at the logs to see what's going on.

rretsiem commented 11 years ago

@voidfiles I published a post at 19:29 (CEST) and my push-bot subscription to test correct push-config got the information and noticed me. The Atom-Feed isn't cached and displays the new post right now.

Now, 30 minutes later, the Pourover-site still displays the last old published post from Aug 9th.

voidfiles commented 11 years ago

Okay, so I see that we received a push, but there was no POST body, if there isn't a POST body then there is nothing to publish. Which means that it will fallback to polling once every 15 minutes, but for some reason your feed is being cached somewhere between app engine and your server for a longer period of time which is why updates take so long.

I have added more logging so the next time this happens let me know again and I will see if I can dig up any new info.

Sorry that this is taking so long, but your feed seems to be particularly unique.

rretsiem commented 11 years ago

Besides the non-working PuSH, the PourOver-Site still don't show the latest feed entry from 4 days ago. So I'm still curious about a cache problem here. The blog is "accelerated" with CloudFlare, but I explicitly excluded the atom-feed from caching. Even if PuSH is not properly working for my "particularly unique" feed, at some point there should be new data displayed ;)