Is the Content-Type meta tag important if responder headers include a content type?

We are currently setting the content type in our responce headers, a bit like this ...

Content-Type    text/html; charset=utf-8

We also have this at the top of the html pages ...

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
  <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

I left the rest of the page.

I know that we strictly do not need a meta tag at the top of the html page.

However, do I need to leave it there due to known browser errors / problems, etc.? I would like this to be excluded, so that the character encoding is installed in two different places, but you need to be sure that it will not ruin anything.

+3
source share
1 answer

, .

, Content-Type . , , .

+3

Source: https://habr.com/ru/post/1721077/


All Articles