From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: Content-type with charset at showhttpheaders in header.pl Date: Thu, 28 Mar 2013 11:07:07 +0100 Message-ID: <1364465227.1844.98.camel@rice-oxley.tremer.info> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8888585463393124294==" List-Id: --===============8888585463393124294== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi, J=C3=B6rn-Ingo suggested this a couple of weeks ago and this patch got accepted in Core 68: http://git.ipfire.org/?p=3Dipfire-2.x.git;a=3Dcommitdiff;h=3D1d795ec5a9c11f85= 12c77e1b51dfc88678f1f9e0 It's basically the same change of lines in the code. :) -Michael On Thu, 2013-03-28 at 02:09 +0100, Kay-Michael K=C3=B6hler wrote: > I suggest to set the charset with the Content-type. That will make > things go faster with the browsers. >=20 >=20 > Regarding to:=20 > https://developers.google.com/speed/docs/best-practices/rendering#SpecifyCh= arsetEarly >=20 >=20 > Specifying a character set in the HTTP response headers of your HTML > documents allows the browser to begin parsing HTML and executing > scripts immediately. >=20 >=20 > Regards, > Kay-Michael >=20 >=20 > diff --git a/config/cfgroot/header.pl b/config/cfgroot/header.pl > index bbb0eca..7c36820 100644 > --- a/config/cfgroot/header.pl > +++ b/config/cfgroot/header.pl > @@ -164,7 +164,7 @@ > print "Pragma: no-cache\n"; > print "Cache-control: no-cache\n"; > print "Connection: close\n"; > - print "Content-type: text/html\n\n"; > + print "Content-type: text/html; charset=3DUTF-8\n\n"; > } > =20 > sub is_menu_visible($) { > _______________________________________________ > Development mailing list > Development(a)lists.ipfire.org > http://lists.ipfire.org/mailman/listinfo/development --===============8888585463393124294==--