When I moved I redirected all the old feeds – apart from my FeedBurner one – on to the new WordPress ones. My sites full post feed is where I get the bulk of my subscribers – the “old URL(magpiebrain – old full post RSS feed)”:http://www.magpiebrain.com/index_full.xml should be permantently redirected to the new “WordPress feed(magpiebrain – the new full post RSS feed)”:http://www.magpiebrain.com/feed/. When I load the old URL in my browser, it correctly redirects and shows the new content. However Bloglines for some reason has yet to display any new content from my new feed. Perhaps Bloglines is ignoring the 301 redirection from my mod_rewrite rule?
I’ll try and chase this up with Bloglines support, but if anyone can shed any light on it I’d appreciate it.
p(update). _update_: According to a “comment”:http://www.intertwingly.net/blog/2004/02/18/Bloglines#c1077175023 over at Sam Ruby’s site that I’m not the only person to have hit this problem. Hopefully Bloglines support will be able to update their database to reflect the new URL’s. It’s a little worrying though that in the year 2006 internet applications like this still aren’t playing nice with standard HTTP return codes
magpiebrain 
6 Responses to “Bloglines not picking up the new feed?”
But, you aren’t sending a 301:
curl -is ‘http://www.magpiebrain.com/index_full.xml’
HTTP/1.1 200 OK
Date: Thu, 20 Apr 2006 14:41:41 GMT
Server: Apache/1.3.29 (Unix) mod_perl/1.29 mod_become/1.3 DAV/1.0.3 PHP/4.3.9 mod_fastcgi/2.4.2
Last-Modified: Mon, 17 Apr 2006 11:22:24 GMT
ETag: “d6ffa-6e52-44437a70”
Accept-Ranges: bytes
Content-Length: 28242
Content-Type: application/xml
…
So, something with your rewrite rule isn’t 100% correct, because it does redirect in my browser too.
That’s very, very odd. I can’t access my .htaccess from work – but I’ll check it when I get home. Thanks for that Paul.
Even if the redirect isn’t a permanent one, the fact that I do see the new feed when going to the old location implies that Bloglines should still get the new entries…
Paul, are you behind a proxy? This is what I get at home:
OK, I’ve routed everything via FeedBurner now (easier to track stats). The redirects work ok from here – let’s see what happens with Bloglines now…
$ host http://www.magpiebrain.com
http://www.magpiebrain.com has address 193.111.200.151
But, that doesn’t look like the correct address now. So, our DNS cache hasn’t expired yet, and thats why we still see the old content.
ah – that makes sense.
I did change the nameserver settings at the weekend so it should of propogated by now though. I did a whois double check and the nameservers do show up correctly.
Anyway, if you’re seeing the old entry still, then I guess Bloglines could be too.