Comment #3 on issue 20840 by folke.lemaitre: "Oops! This link appears to be broken" on pages that are not broken http://code.google.com/p/chromium/issues/detail?id=20840
Found out the issue. Apparently Chromium is not handling 302 http errors. See result of curl -I HTTP/1.1 302 Found X-Pingback: http://torrentfreak.com/xmlrpc.php Content-Type: text/html; charset=UTF-8 Expires: Wed, 11 Jan 1984 05:00:00 GMT Last-Modified: Wed, 09 Sep 2009 11:21:57 GMT Cache-Control: no-cache, must-revalidate, max-age=0 Pragma: no-cache Location: http://torrentfreak.com/utorrent-iphone-app-rejected-by-apple-goes- underground-090831/ Date: Wed, 09 Sep 2009 11:21:57 GMT Server: lighttpd/1.4.23 -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
