|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #25995 mbstring configuration variables are marked PHP_INI_ALL, but this is false.
Submitted: 2003-10-26 18:31 UTC Modified: 2003-11-02 06:18 UTC
Avg. Score:5.0 ± 0.0
Reproduced:1 of 1 (100.0%)
Same Version:1 (100.0%)
Same OS:1 (100.0%)
From: s dot masugata at digicom dot dnp dot co dot jp Assigned: hirokawa (profile)
Status: Closed Package: mbstring related
PHP Version: 4.3.0 OS: Linux
Private report: No CVE-ID: None
Welcome back! If you're the original bug submitter, here's where you can edit the bug or add additional notes.
If this is not your bug, you can add a comment by following this link.
If this is your bug, but you forgot your password, you can retrieve your password here.
Bug Type:
From: s dot masugata at digicom dot dnp dot co dot jp
New email:
PHP Version: OS:


 [2003-10-26 18:31 UTC] s dot masugata at digicom dot dnp dot co dot jp

output_buffering = Off
output_handler =
mbstring.language             = Japanese
mbstring.encoding_translation = On
mbstring.internal_encoding    = EUC-JP
mbstring.http_input           = pass
mbstring.http_output          = pass
mbstring.detect_order         = SJIS-win,SJIS,eucJP-win,EUC_JP,UTF-8,UTF-7,ISO-2022-JP,JIS,ASCII
mbstring.substitute_character = none
mbstring.func_overload        = 1
mbstring.script_encoding      = SJIS

The value of $POST disregards the contents set up by php.ini, and 
is changed into an internal encoding.

In this setup, it should not be changed into an internal encoding.
However, it will be changed.

My purpose wants to only use the function to change script encoding 
by zend-multibyte into an internal encoding, and the function which 
even input data changes into an internal encoding is not needed.

The transmitted input data may be broken down by this unjust 
operation(for example, the special character by the specific model).

I think that this operation is not specification but a bug with 
it being individual.

It seems that it is fixed in the snapshot in the built on Oct 26,
 2003 20:30 GMT, is it fixed as well as a snapshot when PHP4.3.4 
is released?

thank you.


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2003-10-28 09:26 UTC]
Assigned to Rui, he already had a patch.
It was decided not to go in 4.3.4 though.
 [2003-11-02 06:18 UTC]
This bug has been fixed in CVS.

In case this was a PHP problem, snapshots of the sources are packaged
every three hours; this change will be in the next snapshot. You can
grab the snapshot at
In case this was a documentation problem, the fix will show up soon at

In case this was a website problem, the change will show
up on the site and on the mirror sites in short time.
Thank you for the report, and for helping us make PHP better.

This problem is fixed in PHP4.3.4RC4 and it will be applied also for PHP 4.3.4 Release.
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Sat Apr 20 18:01:29 2024 UTC