5 ms·
All the owner of that blog would have to do would be to change his post to look like a normal robots.txt file and he could happily ban Google (or Yahoo, or whoe
by gojomo 17y ago
All the owner of that blog would have to do would be to change his post to look like a normal robots.txt file and he could happily ban Google (or Yahoo, or whoever) from crawling any page on bit.ly.
No crawler I know of accepts a redirected robots.txt from an alternate domain for rules about the original domain.
- NathanKP 17y agoThat is true, but it must still mess things up to have robots.txt redirected. It would appear that Google and other bots won't have any way of reaching the real robots.txt. And what about sitemap.xml, atom.xml, and other typical files that could also be redirected?
- timf 17y agoThat is bit.ly's problem for not making an exception (assuming they want one in the first place, it's not required), not a general problem.
- jerf 17y ago"And what about sitemap.xml, atom.xml, and other typical files that could also be redirected?" Why not try it? As of this writing, both of those go to other places. I checked the other one that lept to mind, favicon.ico. Bit.ly appears to have hardcoded it (probably in apache configuration or equivalent for whatever server they use), however, try http://bit.ly/faviconico http://bit.ly/faviconico and look at the resulting URL. Looks like a few things were tried by the same guy. Now, pwning the favicon would have been cool.
- mustpax 17y agoIs that part of the robots.txt RFC or just a happy security coincidence? The bit.ly issue seems like a pretty bad bug that ought to be fixed. You also might be able to fool Google Webmaster Tools or other utilities into thinking you own bit.ly. One of the authentication methods I've seen used was the creation of an empty html document in the root directory.
- gojomo 17y agoThe 1994 original proposal is silent on what to do with any unexpected response codes/types. The 1997 internet-draft (never an RFC) suggests the redirect should be followed, but the potential confusion that could cause has meant few, if any, crawlers have followed that guidance. It's more likely to be a webmaster configuration error than real intent.
- davenaylor 17y agoyour wrong basically because a 301 returns "found" Google will follow it and use the data, we will blog it tommorrow with proof