There are two W3C standards covering prefetching for HTML5:
HTML5 methods for prefetch hints:
An issue inherent to indiscriminate link prefetching involves the misuse of "safe" HTTP methods. The HTTP GET and HEAD requests are said to be "safe", i.e., a user agent that issues one of these requests should expect that the request results in no change on the recipient server.36 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.37
Additionally, there are a number of criticisms regarding the privacy and resource usage implications of link prefetching:
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.38
"Preload". w3c.github.io. Retrieved 2016-03-19. https://w3c.github.io/preload/ ↩
"Resource Hints". w3c.github.io. Retrieved 2016-03-19. https://w3c.github.io/resource-hints/ ↩
Nottingham, M. (2010). "Web Linking". RFC 5988. IETF. doi:10.17487/RFC5988. S2CID 367264. Retrieved 2016-03-19. https://tools.ietf.org/html/rfc5988 ↩
"Resource Hints (Example 6)". Resource Hints: W3C Working Draft. W3C. Retrieved 2016-10-31. https://www.w3.org/TR/resource-hints/#fetching-the-resource-hint-link ↩
"Prebrowsing". Steve Souders. 2013-10-07. http://www.stevesouders.com/blog/2013/11/07/prebrowsing/ ↩
"Getting to the Content You Want, Faster in IE11". IEBlog, Microsoft. 2013-12-04. Archived from the original on 2014-05-12. https://web.archive.org/web/20140512221226/http://blogs.msdn.com/b/ie/archive/2013/12/04/getting-to-the-content-you-want-faster-in-ie11.aspx?Redirected=true ↩
"Bug 730101 - Implement prerendering in Firefox". Mozilla. 2014-10-18. https://bugzilla.mozilla.org/show_bug.cgi?id=730101 ↩
Fisher, Darin; Saksena, Gagan. "Link Prefetching in Mozilla: A Server-Driven Approach" (PDF). Retrieved 2014-05-09. http://2003.iwcw.org/papers/fisher.pdf ↩
"Controlling DNS prefetching". Retrieved 2014-05-09. https://developer.mozilla.org/en-US/docs/Controlling_DNS_prefetching ↩
"Web Developer's Guide to Prerendering in Chrome". Retrieved 2014-05-09. https://developers.google.com/chrome/whitepapers/prerender?csw=1 ↩
"Internet Explorer 9 Network Performance Improvements". Retrieved 2014-05-09. http://blogs.msdn.com/b/ie/archive/2011/03/17/internet-explorer-9-network-performance-improvements.aspx ↩
"About Google Instant". Retrieved 2014-05-09. https://www.google.com/insidesearch/features/instant/about.html ↩
Fielding, Roy; Gettys, Jim; Mogul, Jeffrey; Frystyk, Henrik; Masinter, Larry; Leach, Paul; Berners-Lee, Tim (June 1999). "Safe Methods". Hypertext Transfer Protocol—HTTP/1.1. Network Working Group. IETF. p. 50. sec. 9.1.1. doi:10.17487/RFC2616. RFC 2616. Retrieved 2009-12-16. /wiki/Roy_Fielding ↩
various (2009). "Mouseover Prefetch?". Gervase Markham, MozillaZine. Archived from the original on 2009-05-31. Retrieved 2009-12-16. https://web.archive.org/web/20090531005531/http://weblogs.mozillazine.org/gerv/archives/2009/05/mouseover_prefetch.html ↩