Comments on: Bloglines not picking up the new feed? http://www.magpiebrain.com/blog/2006/04/20/bloglines-not-picking-up-the-new-feed/ Sam Newman's blog Wed, 15 Oct 2008 20:13:08 +0000 http://wordpress.org/?v=2.5.1 By: sam http://www.magpiebrain.com/blog/2006/04/20/bloglines-not-picking-up-the-new-feed/#comment-1104 sam Thu, 20 Apr 2006 21:34:26 +0000 http://www.magpiebrain.com/blog/2006/04/20/bloglines-not-picking-up-the-new-feed/#comment-1104 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. 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.

]]> By: Paul Querna http://www.magpiebrain.com/blog/2006/04/20/bloglines-not-picking-up-the-new-feed/#comment-1103 Paul Querna Thu, 20 Apr 2006 20:59:21 +0000 http://www.magpiebrain.com/blog/2006/04/20/bloglines-not-picking-up-the-new-feed/#comment-1103 $ host www.magpiebrain.com 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. $ 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.

]]> By: sam http://www.magpiebrain.com/blog/2006/04/20/bloglines-not-picking-up-the-new-feed/#comment-1102 sam Thu, 20 Apr 2006 18:20:01 +0000 http://www.magpiebrain.com/blog/2006/04/20/bloglines-not-picking-up-the-new-feed/#comment-1102 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... 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…

]]> By: sam http://www.magpiebrain.com/blog/2006/04/20/bloglines-not-picking-up-the-new-feed/#comment-1101 sam Thu, 20 Apr 2006 18:18:23 +0000 http://www.magpiebrain.com/blog/2006/04/20/bloglines-not-picking-up-the-new-feed/#comment-1101 Paul, are you behind a proxy? This is what I get at home: <pre> mini:~ samnewman$ curl -is 'http://www.magpiebrain.com/index_full.xml' HTTP/1.1 301 Moved Permanently Date: Thu, 20 Apr 2006 18:15:20 GMT Server: Apache Location: http://www.magpiebrain.com/feed/ Vary: Accept-Encoding Content-Length: 240 Content-Type: text/html; charset=iso-8859-1 <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>301 Moved Permanently</title> </head><body> <h1>Moved Permanently</h1> <p>The document has moved <a href="http://www.magpiebrain.com/feed/" rel="nofollow">here</a>.</p> </body></html> </pre> Paul, are you behind a proxy? This is what I get at home:

mini:~ samnewman$ curl -is 'http://www.magpiebrain.com/index_full.xml'
HTTP/1.1 301 Moved Permanently
Date: Thu, 20 Apr 2006 18:15:20 GMT
Server: Apache
Location: http://www.magpiebrain.com/feed/
Vary: Accept-Encoding
Content-Length: 240
Content-Type: text/html; charset=iso-8859-1

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<HTML><head>
<title>301 Moved Permanently</title>
</head><body>
<h1>Moved Permanently</h1>
<p>The document has moved <a href="http://www.magpiebrain.com/feed/" rel="nofollow">here</a>.</p>
</body></html>
]]> By: sam http://www.magpiebrain.com/blog/2006/04/20/bloglines-not-picking-up-the-new-feed/#comment-1100 sam Thu, 20 Apr 2006 15:24:11 +0000 http://www.magpiebrain.com/blog/2006/04/20/bloglines-not-picking-up-the-new-feed/#comment-1100 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... 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…

]]> By: Paul Querna http://www.magpiebrain.com/blog/2006/04/20/bloglines-not-picking-up-the-new-feed/#comment-1099 Paul Querna Thu, 20 Apr 2006 14:44:10 +0000 http://www.magpiebrain.com/blog/2006/04/20/bloglines-not-picking-up-the-new-feed/#comment-1099 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. 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.

]]>