|
php.net | support | documentation | report a bug | advanced search | search howto | statistics | random bug | login |
PatchesPull RequestsHistoryAllCommentsChangesGit/SVN commits
[2017-08-16 19:16 UTC] philipp at redfish-solutions dot com
[2017-08-19 04:35 UTC] stas@php.net
-Type: Security
+Type: Bug
-Package: Output Control
+Package: Unknown/Other Function
[2021-07-30 10:52 UTC] cmb@php.net
-Status: Open
+Status: Closed
-Package: Unknown/Other Function
+Package: *Network Functions
-Assigned To:
+Assigned To: cmb
[2021-07-30 10:52 UTC] cmb@php.net
[2021-07-30 10:55 UTC] cmb@php.net
-Package: *Network Functions
+Package: Unknown/Other Function
|
|||||||||||||||||||||||||||||||||||||
Copyright © 2001-2025 The PHP GroupAll rights reserved. |
Last updated: Sat Oct 25 10:00:01 2025 UTC |
Description: ------------ This issue came up in the discussions for bz #74860. Basically, the only type of message explicitly and unequivocally allowed by the Syslog RFC's is NVT ASCII (i.e. hex characters 0x20-0x7E). UTF-8 maybe used in compressed (shortest form) but it must be prefixed with a BOM (0xEF,0xBB,0xBF). Also, see the discussion for PR #2674. Test script: --------------- <?php ini_set("error_log", "syslog"); error_log("h\364pital stra\337e", 0); error_log("this string \321\032\003", 0); ?> Expected result: ---------------- It's not obvious what the correct behavior is in legacy cases which violate the RFC's. Actual result: -------------- Aug 15 14:43:07 ubuntu16 php7.0: h?pital stra?e Aug 15 14:43:07 ubuntu16 php7.0: this string ?#032#003