Req #75922 [Opn->Fbk]: default_charset cannot be disabled in Content-Type

From: Date: Tue, 06 Feb 2018 09:31:50 +0000
Subject: Req #75922 [Opn->Fbk]: default_charset cannot be disabled in Content-Type
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-213829@lists.php.net to get a copy of this message 
Edit report at https://bugs.php.net/bug.php?id=75922&edit=1

 ID:                 75922
 Updated by:         requinix@php.net
 Reported by:        bugs at jth dot net
 Summary:            default_charset cannot be disabled in Content-Type
-Status:             Open
+Status:             Feedback
 Type:               Feature/Change Request
 Package:            PHP options/info functions
 Operating System:   Linux
 PHP Version:        7.1.14
 Block user comment: N
 Private report:     N

 New Comment:

Having default_charset not match the actual charset used is a recipe for disaster. Why aren't
they changing that?


Previous Comments:
------------------------------------------------------------------------
[2018-02-06 09:16:40] bugs at jth dot net

Description:
------------
default_charset in php7 is now a mess being used in two different contexts. It should be two
different options: one for internal encoding and one for enabling/disabling being output in the
Content-Type: header.

The Content-Type: header is overriding the meta tag in the document, which different users are
creating in different charsets using the meta tag. 
php is often used for simple functions not involving or regardless of the charset
e.g. database functions.

It is a nuisance and prone to error having the users to specify the charset both as an unnecessary
header() call and as a meta tag. 




------------------------------------------------------------------------



--
Edit this bug report at https://bugs.php.net/bug.php?id=75922&edit=1

Thread (8 messages)

« previous php.bugs (#213829) next »