Meta refresh

Meta refresh is a method of instructing a web browser to automatically refresh the current web page or frame after a given time interval, using an HTML meta element with the http-equiv parameter set to "refresh" and a content parameter giving the time interval in seconds. It is also possible to instruct the browser to fetch a different URL when the page is refreshed, by including the alternative URL in the content parameter. By setting the refresh time interval to zero (or a very low value), meta refresh can be used as a method of URL redirection.

HTML
Comparisons

History

This feature was originally introduced by Netscape Navigator 1.1 (circa 1995), in a form of HTTP header and corresponding HTML meta HTTP-equivalent element, which allows document author to signal client to automatically reload the document or change to a specified URL after a specified timeout.[1] It is the earliest polling mechanism available for the web, to let user see the latest update in a frequently-changing webpage, such as ones displaying stock price or weather forecast.

While this feature has not ever been standardized, it is supported by default in almost all later web browsers.

Usability

Use of meta refresh is discouraged by the World Wide Web Consortium (W3C), since unexpected refresh can disorient users.[2] Meta refresh also impairs the web browser's "back" button in some browsers (including Internet Explorer 6 and before), although most modern browsers compensate for this (Internet Explorer 7 and higher, Mozilla Firefox, Opera, Google Chrome).

There are legitimate uses of meta-refresh, such as providing updates to dynamic web pages or implementing site controlled navigation of a website without JavaScript. Many large websites use it to refresh news or status updates, especially when dependencies on JavaScript and redirect headers are unwanted.

Examples

Place inside <head> to refresh page after 5 seconds:

<meta http-equiv="refresh" content="5">

Redirect to http://example.com/ after 5 seconds:

<meta http-equiv="refresh" content="5; url=https://example.com/">

Redirect to http://example.com/ immediately:

<meta http-equiv="refresh" content="0; url=https://example.com/">

Drawbacks

Meta refresh tags have some drawbacks:

  • If a page redirects too quickly (less than 2-3 seconds), using the "Back" button on the next page may cause some browsers to move back to the redirecting page, whereupon the redirect will occur again. This is bad for usability, as this may cause a reader to be "stuck" on the last website.
  • A reader may or may not want to be redirected to a different page, which can lead to user dissatisfaction or raise concerns about security.[3]

Alternatives

Meta refresh uses the http-equiv meta tag to emulate the Refresh HTTP header, and as such can also be sent as a header by an HTTP web server, although Refresh is not part of the HTTP standard.

Alternatives exist for both uses of meta refresh.

For redirection

An alternative is to send an HTTP redirection status code, such as HTTP 301 or 302. It is the preferred way to redirect a user agent to a different page. This can be achieved by a special rule in the Web server or by means of a simple script on the Web server.

JavaScript is another alternative, but not recommended, because users might have disabled JavaScript in their browsers.

The simplest way of JavaScript redirect using the onload property of the body tag:

<body onload="window.location = 'http://example.com/'">

<!-- Your content here -->

</body>

For refresh

An alternative method is to provide an interaction device, such as a button, to let the user choose when to refresh the content. Another option is using a technique such as Ajax to update (parts of) the Web site without the need for a complete page refresh, but this would also require that the user enable JavaScript in their browser.

gollark: So```lualocal o = os.pullEventos.pullEvent = coroutine.yield-- after stuffos.pullEvent = o```
gollark: if it does, of course.
gollark: You probably want to revert that when the program *exits*.
gollark: > Which is exactly what they wanted here!Not necessarily, this actually does sound like a case where they might want each task to run in its own coroutines (or would, if their pathfinding did yields).
gollark: I mean, it's great for very simple situations where you want to run two things at once in the simplest case, but often projects want to run a listener "thread" and temporarily spawn tasks to handle them or something and this ends up being constantly reinvented.

References
  1. "An Exploration of Dynamic Documents". Netscape Communications Corporation. Archived from the original on 2002-01-24. Retrieved 2020-04-24.
  2. Core Techniques for Web Content Accessibility Guidelines 1.0 - W3C Note 6 November 2000
  3. Meta Refresh Tag, An About.com article covering the use of the tag for page reloading or redirection
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.