Re: Content-type with charset at showhttpheaders in header.pl

Re: Content-type with charset at showhttpheaders in header.pl

[Michael Tremer]

[-- Attachment #1: Type: text/plain, Size: 1380 bytes --]

Hi,

Jörn-Ingo suggested this a couple of weeks ago and this patch got
accepted in Core 68:

http://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=1d795ec5a9c11f8512c77e1b51dfc88678f1f9e0

It's basically the same change of lines in the code. :)

-Michael

On Thu, 2013-03-28 at 02:09 +0100, Kay-Michael Köhler wrote:
> I suggest to set the charset with the Content-type. That will make
> things go faster with the browsers.
> 
> 
> Regarding to: 
> https://developers.google.com/speed/docs/best-practices/rendering#SpecifyCharsetEarly
> 
> 
> Specifying a character set in the HTTP response headers of your HTML
> documents allows the browser to begin parsing HTML and executing
> scripts immediately.
> 
> 
> Regards,
> Kay-Michael
> 
> 
> 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=UTF-8\n\n";
>  }
>  
>  sub is_menu_visible($) {
> _______________________________________________
> Development mailing list
> Development(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development