user agent that issues one of these requests should expect that the request results in no change on the recipient server. However, it is common for website operators to use these requests outside of this constraint. Plain hyperlinks (which almost universally result in GET requests) are often used to implement logout functionality and account verification, e.g., when a user completes an account creation form, and an automated service sends a verification e-mail to the user's given e-mail address. Similarly, it is entirely possible for a hosting service to provide a Web front end to manage files, including links that delete one or more files. Users who visit pages containing these types of links, (whilst using a browser which employs an indiscriminate link prefetcher), might find that they have been logged out or that their files have been deleted. Additionally, there are a number of criticisms regarding the privacy and resource usage implications of link prefetching: Cookies set or sent to third parties compromise Web privacy. Enables essentially/borderline Zero-click attack malware installation via 0day merely because a malware-spreading link is prefetched. Users and website operators who pay for the amount of bandwidth they use find themselves paying for traffic for pages the user might not actually visit, and advertisers might pay for viewed ads on sites that are never visited. Web statistics such as browser usage, search engine referers, and page hits may become less reliable due to registering page hits that were never seen by the user. Users may be exposed to more security risks by downloading more pages, or from un-requested sites (additionally compounded as drive-by downloads become more advanced and diverse). Users may violate acceptable-use policies of their network or organisation if prefetching accesses unauthorised content. In the case of mobile devices or for users with a limited bandwidth allowance, prefetching may result in an unnecessary costly drain on limited bandwidth. It is possible for implementations to prefetch links even when they are not specified as prefetch links. In the case of prerendering, Google warns that improper use may result in the aforementioned increased bandwidth usage, slower loading of other links, and slightly stale content. See also Cache prefetching References External links Mozilla Link Prefetching FAQ Test for Prefetch support Prerender and prefetch support in Internet Explorer 11 A WordPress plugin that implements the true dynamic prerender meta tag Hypertext Transfer Protocol