Bug #70892 [Nab]: does not show error text

From: Date: Fri, 13 Nov 2015 15:16:01 +0000
Subject: Bug #70892 [Nab]: does not show error text
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-197241@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=70892&edit=1 ID: 70892 User updated by: y dot korotia at hotmail dot com Reported by: y dot korotia at hotmail dot com Summary: does not show error text Status: Not a bug Type: Bug Package: Filesystem function related Operating System: Win 8.1 x64 PHP Version: 5.6.15 Block user comment: N Private report: N New Comment: i'm not newcomer in sense of it. i'm zend certified in php5.3, i'm just started to play with non ascii chars in different places. as i didn't see php threw me error of bad filename (non ascii chars), your statement "to use ascii filenames" is wrong. i hope you see my point. about charset of content. content in my files is UTF-8 w/o BOM. php.ini contains defaults (so it is utf-8 too). Server cannot send request url in cp1251, because according to rfc3986 and rfc3629 URI is pure ASCII with encoding non ascii chars (maybe i'm wrong here). Url rewrite has nothing to do with PHP itself too. also, i didn't find option to tell PHP what is my filesystem's codepage. i don't really understand connection between file content encoding and filesystem codepage (in fact, encoding for filenames) you are trying to point me out. so, i'll put it back to bug for one more answer regards Previous Comments: ------------------------------------------------------------------------ [2015-11-11 17:04:32] ab@php.net ah, and another factor is also whether your PHP source file itself were in the same charset as the filename you're trying to include :) Probably too much for a new comer. So really, you shouldn't over complicate much at the start ... Thanks. ------------------------------------------------------------------------ [2015-11-11 17:01:07] ab@php.net Thanks for the report. You should use ASCII filenames anyway. But then - the charset you configured for the PHP output and the charset of the actual content you output is different. Same for server or console. Then - if your browser sends the request URL in cp1251 or utf8 makes another difference. If you're just starting to play with PHP, you definitely should use ASCII for filenames, etc. When you learn more about how charset handling works at various places, you'll be able to configure it a correct way. Fe in this case i'd be rather doing filenames in ascii in any case, and then using some URL rewrite module to produce URLs like http://моя-страница/старт and to route them to a corresponding controller. Thanks. ------------------------------------------------------------------------ [2015-11-11 16:43:54] y dot korotia at hotmail dot com also to get URL path i have to do next urldecode(iconv('cp1251','utf-8', $_SERVER['REQUEST_URI'])) anyway, i'm stopping to comment on this, looks like a bug house regards ------------------------------------------------------------------------ [2015-11-11 16:24:30] y dot korotia at hotmail dot com same with PHP-7rc6 it looks like the nature of this issue is the same as in require() which cannot find file until i use iconv() on filename in utf8 encoded code file like require iconv('utf-8', 'Windows-1251', 'стартова.php'); p.s. this is not a critical bug for me, i just play with php, but i find it as a bug ------------------------------------------------------------------------ [2015-11-11 15:36:02] y dot korotia at hotmail dot com Description: ------------ if i use Cyrillic filename PHP does not show error message when thrown also filename is not possible to read i use Win 8.1/IIS x64, php is NTS x86 Test script: --------------- (1) file: index.php code: throw new \Exception('msg'); produces: Fatal error: Uncaught exception 'Exception' with message 'msg' in C:\..\index.php on line 2 (2) file: стартова.php code: throw new \Exception('msg'); produces: Fatal error: in C:\..\��������.php on line 2 Expected result: ---------------- i expect to see error message and readable file name Actual result: -------------- no error message and unreadable filename ------------------------------------------------------------------------ -- Edit this bug report at https://bugs.php.net/bug.php?id=70892&edit=1

« previous php.bugs (#197241) next »