html Alternate of http-equiv = “pragma” and http-equiv = “cache-control” in meta tags

Posted By
Date November 19, 2021October 2, 2025
Comments 0

Since this meta tag is only directed for IE all you need to do is add a IE conditional. When IE market sharing was decreasing, MS realized staying standard incompatible was not a good idea. Therefore MS started to release new IE version (IE8/IE9/IE10) respecting more and more the web standards.

Step 1: Create a new form or quiz

With the changes Microsoft has made to its browsers (more on those below). The timer starts when the page is completely loaded, which is after the load and pageshow events have both fired.See Accessibility concerns for more information. Through the use of the expiration ate in the past, the browser should regard the file as expired and not cache it. Accordingly, the content has to be downloaded each time the page is loaded or refreshed.

Using the Cache-Control Meta Tag

DOCTYPE alone cannot do that; you will end up in one of the Compatibility View modes in these cases regardless of DOCTYPE.
Whenever possible ensure the cache-control HTTP header is set with no-cache, no-store, must-revalidate, private; and that the pragma HTTP header is set with no-cache.
Browser caching, while speeding up website loading, poses challenges in serving recent updates.
By default these settings force all intranet sites into Compatibility View regardless of DOCTYPE.

As this answer is now 10+ years old my recommendation would be to leave this tag out altogether, unless you must support old legacy browsers. To create or edit your form with others, you can share your form with collaborators. Whoever you invite can edit any part of your form, including responses and where they are saved.

Microsoft Edge, the browser that replaced IE11, only honors the X-UA-Compatible meta tag in certain circumstances. If there is no difference, I suppose I can just ignore the X-UA-Compatible meta header, since I just want it to be rendered in most standard mode in all IE versions. In the fast-paced internet era, delivering up-to-date content to users is crucial. Browser caching, while speeding up website loading, poses challenges in serving recent updates. Fortunately, developers can leverage meta HTML tags to control caching behaviour, ensuring users receive the latest content promptly. This article explores the significance of browser caching and demonstrates the use of meta HTML tags to enhance web speed.

It places Internet Explorer into the highest supported document mode. Edge most is most useful for regularly maintained websites that are routinely tested for interoperability between multiple browsers, including Internet Explorer. However, cacheing headers are unreliable in meta elements; for one, any web proxies between the site and the user will completely ignore them.

Note Starting with IE11, edge mode is considered the preferred document mode. (In earlier versions, it was considered experimental.) To learn more, see Document modes are deprecated. Starting with Windows Internet Explorer 8, some web developers used the edge mode meta element to hide the Compatibility View button on the address bar. As of IE11, this is no longer necessary as the button has been removed from the address bar.

If you are using the X-UA-Compatible META tag you want to place it as close to the top of the page’s HEAD as possible. Internet Explorer begins interpreting markup using the latest version. When Internet Explorer encounters the X-UA-Compatible META tag it starts over using the designated version’s engine. This is a performance hit because the browser must stop and restart analyzing the content.

What kind of Experience do you want to share?

Caching headers are unreliable in meta elements; for one,any web proxies between the site and the user will completely ignorethem. You should always use a real HTTP header for headers such asCache-Control and Pragma. Don’t do this, as the X-UA-Compatible header is only supported starting with Windows Internet Explorer 8.

These two rules are simplified but they are easy to remember and to verify. Despite MSDN docs stating you can put title and other meta tags before this one, I would not recommend to do so. This answer is based on examining the complete rules for deciding document mode in IE8, IE9, and IE10.

For modern web browsers (After IE

Make sure to update sites that rely on legacy features and document modes to reflect modern standards. Starting with IE11, edge mode is the preferred document mode; it represents the highest support for modern standards available to the browser. Tip If you want all supported versions of Internet Explorer to open your pages in standards mode, use the HTML5 document type declaration, as shown in the earlier example. Note that this is functionally equivalent to using the HTML5 doctype.

You should always use a real HTTP header for headers such as Cache-Control and Pragma. Use the following value to display the webpage in edge mode, which is the highest standards mode supported by Internet Explorer, from Internet Explorer 6 through IE11. However, at this time, Mozilla started Firefox development respecting as much as possible all the web standards (other browser were implemented to render pages as done by IE6).

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Forms quick start guides

If both the meta tag and the HTTP header are specified, the meta tag takes precedence.
They include directives to declare what should be cacheable, what may be stored by caches, modifications of the expiration mechanism, and revalidation and reload controls.
With our latest platform updates, the need for legacy document modes is primarily limited to Enterprise legacy web apps.
Google Chrome Frame seamlessly enhances your browsing experience in Internet Explorer.
Fortunately, developers can leverage meta HTML tags to control caching behaviour, ensuring users receive the latest content promptly.

If copied, the second would overwrite the first and thefourth would overwrite the third because of the http-equivdeclarations AND fail with the W3C validator. At most, one could haveone of each http-equiv declarations; pragma, cache-control andexpires. These are completely outdated when using modern up to date browsers.After IE9 anyway. Chrome and Firefox specifically does not work with these as you would expect, if at all. Connect and share knowledge within a single location that is structured and easy to search. To edit forms and analyse vegas casino apk download responses with others, you can share your form with collaborators.

With the changes in Microsoft Edge to no longer support document modes in most cases, Microsoft has a tool to scan your site to check and see if it has code that is not compatible with Edge. Edge mode was introduced in Internet Explorer 8 and has been available in each subsequent release. Note that the features supported by edge mode are limited to those supported by the specific version of the browser rendering the content. If you currently use the x-ua-compatible header to target a legacy document mode, it’s possible your site won’t reflect the best experience available with IE11. The X-UA-Compatible meta tag allows web authors to choose what version of Internet Explorer the page should be rendered as.

When someone takes your survey, they will be required to enter their email address before they submit the form. This goes in your root .htaccess file but if you have access to httpd.conf that is better. This code uses the FilesMatch directive and the Header directive to add Cache-Control Headers to certain files. Public – may be cached in public shared caches.Private – may only be cached in private cache.No-Cache – may not be cached.No-Store – may be cached but not archived. This answer was posted several years ago and now the question really should be should you even consider using the X-UA-Compatible tag on your site?

For many years (2000 to 2008), IE market share was more than 80%. And IE v6 was considered as a de facto standard (80% to 97% market share in 2003, 2004, 2005 and 2006 for IE6 only, more market share with all IE versions). The list is just examples of different techniques, it’s not for directinsertion.

Note that looking at the DOCTYPE is the very last fallback for deciding the document mode. If both the meta tag and the HTTP header are specified, the meta tag takes precedence. The difference is that if you only specify the DOCTYPE, IE’s Compatibility View Settings take precedence. By default these settings force all intranet sites into Compatibility View regardless of DOCTYPE. There’s also a checkbox to use Compatibility View for all websites, regardless of DOCTYPE.

Because it forces all pages to be opened in standards mode, regardless of the version of Internet Explorer, you might be tempted to use edge mode for all pages viewed with Internet Explorer. Don’t do this, as the X-UA-Compatible header is only supported starting with Internet Explorer 8. As we announced in August 2013, we are deprecating document modes as of IE11. With our latest platform updates, the need for legacy document modes is primarily limited to Enterprise legacy web apps. IE will still honor document modes served by intranet sites, sites on the Compatibility View list, and when used with Enterprise Mode only. Starting with IE11, document modes are deprecated and should no longer be used, except on a temporary basis.