How can an HTTP header be specified using a meta tag?

<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">

The <meta> tag with the http-equiv attribute is used to simulate HTTP headers. This can be useful when you do not have direct control over the HTTP server configuration. The http-equiv attribute specifies the name of the HTTP header to simulate, and the content attribute contains the corresponding value.

Some common examples of usage:

• Content-Type: Specifies the content type and character encoding of the page.

  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  

• Refresh: Automatically reloads the page or redirects to another URL.

  <meta http-equiv="Refresh" content="5; url=https://example.com/"> // Reloads after 5 seconds with a redirect to example.com
  

• Expires: Indicates the date and time after which the document is considered outdated. Used for caching.

  <meta http-equiv="Expires" content="Fri, 20 Mar 2024 12:00:00 GMT">
  

• Set-Cookie: Sets cookies. (Although this is less common and not always recommended for setting cookies).

  <meta http-equiv="Set-Cookie" content="name=value; expires=date; path=/">
  

Important: Using <meta http-equiv> has limitations:

• Not all HTTP headers can be simulated this way.
• HTTP headers set at the server level take precedence over <meta> tags with http-equiv.
• Using meta tags for HTTP headers can affect performance, as the browser needs to read the HTML first before applying these "headers".

Whenever possible, it is preferable to configure HTTP headers directly on the web server.