Bad value cache-control for attribute http-equiv on element meta

Pawan

I dont want my HTML5 pages to be cached , so i am using these tags under my HTML file

<!DOCTYPE html>
<head>
<meta charset="utf-8">
<meta http-equiv="cache-control" content="max-age=0" />
<meta http-equiv="cache-control" content="no-cache" />
<meta http-equiv="expires" content="0" />
<meta http-equiv="expires" content="Tue, 01 Jan 1980 1:00:00 GMT" />
<meta http-equiv="pragma" content="no-cache" />
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<script src="js/jquery-1.10.2.min.js"></script>

</head>

When i validated these with http://validator.w3.org/check ,

its saying as

Bad value cache-control for attribute http-equiv on element meta.

<meta http-equiv="cache-control" content="max-age=0" />

Bad value cache-control for attribute http-equiv on element meta.

<meta http-equiv="cache-control" content="no-cache" />

Bad value expires for attribute http-equiv on element meta.

<meta http-equiv="expires" content="0" />

Bad value expires for attribute http-equiv on element meta.

<meta http-equiv="expires" content="Tue, 01 Jan 1980 1:00:00 GMT" />

Bad value pragma for attribute http-equiv on element meta.

<meta http-equiv="pragma" content="no-cache" />

Could you please let me know how to resolve this ??

Kuba Wyrostek

HTML5 has very small set of values available for http-equiv attribute for meta property. It's not that you can take any possible HTTP header and use it this way. Although browser may and support many non-standard values, it's simply non spec-conformant.

Information here: http://www.w3.org/TR/html5/document-metadata.html#standard-metadata-names in p. 4.2.5.3 Pragma directives.

What you can probably do is - depending on used server technology - add those headers to HTTP response. How - this depends on whether your page is dynamically generated or is a static file. In the second case it depends on server software capabilities.

Collected from the Internet

Please contact debug[email protected] to delete if infringement.

edited at
0

Comments

0 comments
Login to comment

Related

From Dev

"Bad value expires for attribute http-equiv on element meta"

From Dev

W3C validator: "Bad value robots for attribute name on element meta"

From Dev

Are there HTML5 compliant alteratives to the http-equiv Cache-Control and Pragma directives?

From Dev

in Node.js, how to get set-cookie value in a <meta http-equiv> tag

From Dev

Cache control meta tags

From Dev

Using Cache-Control in HTTP per Element

From Dev

Bad value pagination for attribute role on element nav

From Dev

Bad value pagination for attribute role on element nav

From Dev

What is the http-equiv attribute? Why is it named that?

From Dev

What is the http-equiv attribute? Why is it named that?

From Dev

Bad value for attribute action on element form: Must be non-empty

From Java

<meta charset="utf-8"> vs <meta http-equiv="Content-Type">

From Dev

Bad value for attribute autofocus

From Java

What does <meta http-equiv="X-UA-Compatible" content="IE=edge"> do?

From Dev

using <meta http-equiv="X-UA-Compatible" content="IE=edge" /> with Wicket not working

From Dev

What will this do: <meta http-equiv="X-UA-Compatible" content="IE=edge">?

From Dev

Is <html lang="de-DE"> equal to <meta http-equiv="language" content="DE">?

From Dev

Pass JS variable into meta tag http-equiv=refresh into url field

From Dev

"Attribute itemprop not allowed on element meta at this point"

From Dev

http-equiv - what's equiv stand for?

From Dev

"Bad value for attribute src on element img: Must be non-empty", for dynamically generated img src

From Dev

JAXB Attribute as Element Value

From Dev

Cache-control max-age meta tag not registering

From Dev

Scope of Cache-Control meta tag in HTML file

From Dev

Does meta http-equiv="X-UA-Compatible" content="IE=edge" impact on non-IE explorer?

From Dev

Does meta http-equiv="X-UA-Compatible" content="IE=edge" impact on non-IE explorer?

From Dev

The value "<" is not valid in an attribute on PasswordBox control

From Dev

validate element value with attribute value

From Dev

http-equiv="content-language" doesn't work (element.lang = "")

Related Related

  1. 1

    "Bad value expires for attribute http-equiv on element meta"

  2. 2

    W3C validator: "Bad value robots for attribute name on element meta"

  3. 3

    Are there HTML5 compliant alteratives to the http-equiv Cache-Control and Pragma directives?

  4. 4

    in Node.js, how to get set-cookie value in a <meta http-equiv> tag

  5. 5

    Cache control meta tags

  6. 6

    Using Cache-Control in HTTP per Element

  7. 7

    Bad value pagination for attribute role on element nav

  8. 8

    Bad value pagination for attribute role on element nav

  9. 9

    What is the http-equiv attribute? Why is it named that?

  10. 10

    What is the http-equiv attribute? Why is it named that?

  11. 11

    Bad value for attribute action on element form: Must be non-empty

  12. 12

    <meta charset="utf-8"> vs <meta http-equiv="Content-Type">

  13. 13

    Bad value for attribute autofocus

  14. 14

    What does <meta http-equiv="X-UA-Compatible" content="IE=edge"> do?

  15. 15

    using <meta http-equiv="X-UA-Compatible" content="IE=edge" /> with Wicket not working

  16. 16

    What will this do: <meta http-equiv="X-UA-Compatible" content="IE=edge">?

  17. 17

    Is <html lang="de-DE"> equal to <meta http-equiv="language" content="DE">?

  18. 18

    Pass JS variable into meta tag http-equiv=refresh into url field

  19. 19

    "Attribute itemprop not allowed on element meta at this point"

  20. 20

    http-equiv - what's equiv stand for?

  21. 21

    "Bad value for attribute src on element img: Must be non-empty", for dynamically generated img src

  22. 22

    JAXB Attribute as Element Value

  23. 23

    Cache-control max-age meta tag not registering

  24. 24

    Scope of Cache-Control meta tag in HTML file

  25. 25

    Does meta http-equiv="X-UA-Compatible" content="IE=edge" impact on non-IE explorer?

  26. 26

    Does meta http-equiv="X-UA-Compatible" content="IE=edge" impact on non-IE explorer?

  27. 27

    The value "<" is not valid in an attribute on PasswordBox control

  28. 28

    validate element value with attribute value

  29. 29

    http-equiv="content-language" doesn't work (element.lang = "")

HotTag

Archive