| > 1) Removal of the referrer (the anonymising redirect) Should really done by a browser maybe like an attribute on a link but fair enough. > 2) Redirects within a site when content moves, but the redirect service offers a permalink shortened URL. As only they can generate the URL you can trust that the destination is as safe as the source (the intra-site trusted redirect with vanity URLs) Just make the original url not move... > 3) Self-healing of the web, if a URL becomes broken the redirect service may be able to figure out or suggest a replacement, or offer a cached version of the destination or a link to the web archive (the self-healing redirect) Ideally just better one on the browser and is done in say like chrome. I doubt there's any that were manually updated. > 4) Protect users against malware and spam by cancelling a redirect if the URL is reported (the 'for the user' gateway redirect) This is done in browsers anyway. And even if when would this work? Presumably they are getting this through some trusted medium otherwise what's to prevent them just getting a bad url? And if they are why not just check before? |
http://www.w3.org/TR/html5/links.html#link-type-noreferrer