Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.php > #19189
| Path | csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail |
|---|---|
| From | "J.O. Aho" <user@example.net> |
| Newsgroups | comp.lang.php |
| Subject | Re: [docker] error_log() not write inside web page |
| Date | Wed, 30 Nov 2022 11:26:30 +0100 |
| Lines | 47 |
| Message-ID | <juopemFr2ogU2@mid.individual.net> (permalink) |
| References | <tltt21$1t5m$1@gioia.aioe.org> <jun7rtFtd3rU4@mid.individual.net> <tm77g8$1qkj$1@gioia.aioe.org> |
| Mime-Version | 1.0 |
| Content-Type | text/plain; charset=UTF-8; format=flowed |
| Content-Transfer-Encoding | 8bit |
| X-Trace | individual.net A6IsG54+XkeaQwi7GotKNgxmavdD/Xs3K15ZpkgJKeThjsKa7I |
| Cancel-Lock | sha1:iUAwTUa0yrMyOwSEZn5O6wEIBPQ= |
| User-Agent | Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.5.0 |
| Content-Language | en-US-large |
| In-Reply-To | <tm77g8$1qkj$1@gioia.aioe.org> |
| Xref | csiph.com comp.lang.php:19189 |
Show key headers only | View raw
On 30/11/2022 10.24, SupaPlex wrote: > Il 29/11/22 21:20, Arno Welzel ha scritto: >> Because error_log() does not produce any output: >> >> <https://www.php.net/manual/en/function.error-log.php> >> >> "error_log — Send an error message to the defined error handling >> routines" >> >> And the error handling routines may not send the log message to the >> output but only to the error log which is *not* send via HTTP to the >> client. >> >> Next time please read the PHP manuals first, before asking here. > > Practically error_log() varies its behavior based on the API server > (https://www.php.net/manual/en/function.php-sapi-name.php)? I would say the API that the web server uses to talk with the PHP engine will not change the behavior, what you are looking for is ; This directive controls whether or not and where PHP will output errors, ; notices and warnings too. Error output is very useful during development, but ; it could be very dangerous in production environments. Depending on the code ; which is triggering the error, sensitive information could potentially leak ; out of your application such as database usernames and passwords or worse. ; For production environments, we recommend logging errors rather than ; sending them to STDOUT. ; Possible Values: ; Off = Do not display any errors ; stderr = Display errors to STDERR (affects only CGI/CLI binaries!) ; On or stdout = Display errors to STDOUT ; ; Development Value: On ; Production Value: Off ; https://php.net/display-errors display_errors = Off -- //Aho
Back to comp.lang.php | Previous | Next — Previous in thread | Find similar | Unroll thread
[docker] error_log() not write inside web page SupaPlex <old@gamer.s> - 2022-11-26 21:30 +0100
Re: [docker] error_log() not write inside web page Arno Welzel <usenet@arnowelzel.de> - 2022-11-29 21:20 +0100
Re: [docker] error_log() not write inside web page SupaPlex <old@gamer.s> - 2022-11-30 10:24 +0100
Re: [docker] error_log() not write inside web page SupaPlex <old@gamer.s> - 2022-11-30 10:33 +0100
Re: [docker] error_log() not write inside web page "J.O. Aho" <user@example.net> - 2022-11-30 11:26 +0100
csiph-web