From d2f597235a1d384cf1d69cb51a74c22755c0c11c Mon Sep 17 00:00:00 2001 From: Vincent Herbet Date: Wed, 5 Feb 2020 17:52:58 +0100 Subject: [PATCH] Do no use non-ASCII characters in loaded configs I had an issue with Certbot (let's encrypt) which failed to reload nginx due to a non-ASCII character in a loaded config file. E.g.: `Attempting to renew cert (domain.com) from /etc/letsencrypt/renewal/domain.com.conf produced an unexpected error: 'ascii' codec can't decode byte 0xe2 in position 762: ordinal not in range(128). Skipping.` I found this character using `grep -r -P '[^\x00-\x7f]' /etc/nginx`. --- h5bp/security/x-frame-options.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/h5bp/security/x-frame-options.conf b/h5bp/security/x-frame-options.conf index ae37b7f..6d98b9a 100644 --- a/h5bp/security/x-frame-options.conf +++ b/h5bp/security/x-frame-options.conf @@ -14,7 +14,7 @@ # https://tools.ietf.org/html/rfc7034#section-2.1. # # Keep in mind that while you could send the `X-Frame-Options` header for all -# of your website’s pages, this has the potential downside that it forbids even +# of your website's pages, this has the potential downside that it forbids even # non-malicious framing of your content (e.g.: when users visit your website # using a Google Image Search results page). #