From 6b2d95f2456a40af4e0c09fd09d8a1b09d5acd7f Mon Sep 17 00:00:00 2001 From: Simon C Date: Wed, 11 Mar 2020 16:53:51 +0100 Subject: [PATCH] fix: Avoid http-equiv tags MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit HTTP headers are more efficient than the http-equiv meta tags. The tags The http-equiv meta tags allow to communicate to the web browser information equivalent to the ones of HTTP headers. For example, the meta will have the same consequences than the HTTP Content-Type header. Two points don’t stimulate the use of http-equiv meta tags: Going through the meta requires to interpret the beginning of the HTML page, which is slower than going through the HTTP headers in terms of performance If the HTTP header is already present, the meta is ignored In which cases are the useful? Only one case can justify the presence of these meta tags: if you don’t have access to the configuration of your server, and that is to say to the HTTP headers. However, we advice you to use a configurable server so that you can establish the most efficient site possible. This page contains 1 http-equiv meta tag. If possible, you should replace it: x-ua-compatible --- nginx-default.conf | 2 ++ themes/hugo-theme-lowtech | 2 +- 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/nginx-default.conf b/nginx-default.conf index a1ad5d1..4e8e411 100644 --- a/nginx-default.conf +++ b/nginx-default.conf @@ -23,6 +23,8 @@ server { # https://www.cyberciti.biz/faq/nginx-set-http-content-type-response-header-to-charset-utf8/ charset UTF-8; + add_header X-UA-Compatible "IE=Edge,chrome=1"; + #Caching (save html pages for 7 days, rest as long as possible, no caching on frontpage) expires $expires; diff --git a/themes/hugo-theme-lowtech b/themes/hugo-theme-lowtech index f4c5d9f..8da32f8 160000 --- a/themes/hugo-theme-lowtech +++ b/themes/hugo-theme-lowtech @@ -1 +1 @@ -Subproject commit f4c5d9f12282695344134bd3ffd064ca4d1e1fe1 +Subproject commit 8da32f8afd91ef803551fdf592f2d3efc70773c6