Comments on: Backup Servers on the CSM http://aconaway.com/2008/06/26/backup-servers-on-the-csm/ Not something you want to hear Thu, 20 Nov 2008 11:47:18 +0000 http://wordpress.org/?v=2.6.2 By: Aaron Conaway http://aconaway.com/2008/06/26/backup-servers-on-the-csm/#comment-2652 Aaron Conaway Fri, 27 Jun 2008 12:35:50 +0000 http://aconaway.com/2008/06/26/backup-servers-on-the-csm/#comment-2652 Good point, Ivan. There is a definite art to corralling search engine spiders. Part of the "we suck" setup could also be a robots.txt that tells everyone to go away. That would keep the well-behaved spiders from caching the page. The misbehaving ones are a different story, though. Good point, Ivan. There is a definite art to corralling search engine spiders.

Part of the “we suck” setup could also be a robots.txt that tells everyone to go away. That would keep the well-behaved spiders from caching the page. The misbehaving ones are a different story, though.

]]> By: Ivan Pepelnjak http://aconaway.com/2008/06/26/backup-servers-on-the-csm/#comment-2647 Ivan Pepelnjak Fri, 27 Jun 2008 08:22:59 +0000 http://aconaway.com/2008/06/26/backup-servers-on-the-csm/#comment-2647 Just a minor detail: if you use the "we're sorry, but we suck" approach, make sure the web page returns HTTP error code 503 (500 is also OK, but 503 is better) with the Retry-After header. If you return a regular HTML page, it might get cached by search engines instead of your actual content. Just a minor detail: if you use the “we’re sorry, but we suck” approach, make sure the web page returns HTTP error code 503 (500 is also OK, but 503 is better) with the Retry-After header. If you return a regular HTML page, it might get cached by search engines instead of your actual content.

]]>