From 85b5988dc71d8c01b60423ec1a7dbb03830365d0 Mon Sep 17 00:00:00 2001 From: Glenn Strauss Date: Mon, 9 May 2022 21:36:44 -0400 Subject: [multiple] use preferred syntax for Content-Type use preferred syntax for Content-Type: .../charset=... (match preferred syntax specified in upcoming HTTP spec revision) --- doc/scripts/create-mime.conf.pl | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'doc') diff --git a/doc/scripts/create-mime.conf.pl b/doc/scripts/create-mime.conf.pl index dcadf297..d38e996d 100755 --- a/doc/scripts/create-mime.conf.pl +++ b/doc/scripts/create-mime.conf.pl @@ -9,7 +9,7 @@ use strict; my $verbose = 0; foreach (@ARGV) { $verbose = 1 if ($_ eq "-v"); } -# text/* subtypes to serve as "text/...; charset=utf-8" +# text/* subtypes to serve as "text/...;charset=utf-8" # text/html IS NOT INCLUDED: html has its own method for defining charset # (), but the standards specify that content-type in HTTP wins over # the setting in the html document. @@ -147,7 +147,7 @@ sub add { sub print_type { my ($extension, $mimetype) = @_; if ($mimetype =~ /^text\/(.*)$/) { - $mimetype .= "; charset=utf-8" if $text_utf8{$1}; + $mimetype .= ";charset=utf-8" if $text_utf8{$1}; } print "\t\"${extension}\" => \"${mimetype}\",\n"; -- cgit v1.2.1