[php-src] Issue #8120: mysqli blank error

From: Date: Mon, 21 Feb 2022 23:25:05 +0000
Subject: [php-src] Issue #8120: mysqli blank error
Groups: php.bugs 
Request: Send a blank email to php-bugs+get-239952@lists.php.net to get a copy of this message
Issue: https://github.com/php/php-src/issues/8120 Comment Author: kamil-tekiela >have you studied the OWAPS top 10, one of the first things is to disable all errors on >production because it exposes code. The [OWASP cheatsheet for PHP](https://cheatsheetseries.owasp.org/cheatsheets/PHP_Configuration_Cheat_Sheet.html) supports what I have said. You absolutely should have error reporting enabled in production and it will not expose code to users. **IF** you have display_errors enabled though, it might expose backtrace and even parameter values. >you only encounter this when running it from the command line and it should NOT be happening. Not sure what you mean, but we don't see any bug from your description. PHP seems to be working as designed and is throwing the error properly. Whether you want to see that error, just its last line, or nothing at all is up to you. This bug report will remain closed as this seems to be all just a misunderstanding of what exec() returns.

« previous php.bugs (#239952) next »