Bug #68320 [Opn->Nab]: str_replace not binary safe

Edit report at https://bugs.php.net/bug.php?id=68320&edit=1 ID: 68320 Updated by: requinix@php.net Reported by: zf at ancientrock dot org Summary: str_replace not binary safe -Status: Open +Status: Not a bug Type: Bug Package: Scripting Engine problem Operating System: CentOS 6.5 x64 PHP Version: 5.6.2 Block user comment: N Private report: N New Comment: str_replace() is binary-safe. The problem is that the encoding you're using is not safe for writing PHP code in*, and in fact you'll get similar problems with other programming languages. GBK with a database can even expose you to SQL injection. You need to use something other than GBK for your code. Like UTF-8 or -16. * Briefly, GBK will encode some characters into \xHH\x5C (ie, a byte followed by a \x5C byte). \x5C is a backslash and that can cause problems because it's used for escape sequences in strings. Previous Comments: ------------------------------------------------------------------------ [2014-10-28 23:50:05] zf at ancientrock dot org Description: ------------ While using str_replace to replace string (CP936 encoding), the result leading bad encoding text output Test script: --------------- <?php //GBK encoding str_replace test; save this file into GBK encoding and run it $str = "退党保平安，你心里有不舒服的时候就说出来，为什么不舒服，女孩子都有点这样的脾气的"; var_dump(str_replace('退党', '**', $str)); Expected result: ---------------- display: 保平安，你心里有不舒服的时候就说出来，为什么不舒服，女孩子都有点这样的脾气的 Actual result: -------------- the text was broken, and can not readable ------------------------------------------------------------------------ -- Edit this bug report at https://bugs.php.net/bug.php?id=68320&edit=1