Re: Request: Prevention of FPD in Fatal/Parse/Other Errors
| From: | Rowan Collins | Date: | Mon, 04 Jul 2016 09:28:08 +0000 |
| Subject: | Re: Request: Prevention of FPD in Fatal/Parse/Other Errors | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-94369@lists.php.net to get a copy of this message | ||
Hi Ted,
On 30/06/2016 17:17, Ted Phillips wrote:
- Include a new ini directive for fpd_prevention, defaulting to On or a string for replacement, like the ever-popular [path] [...]
- Automatically register the containing path of PHP_SELF at initialization. This will deal will fatal errors occurring before the application can specify its paths, such as when max_input_vars is exceeded by a crafted request.Could you give some concrete examples of what an error message would look like before and after this change? I'm trying to understand what the tradeoff might be for users trying to track down where an error has occurred. Regards, -- Rowan Collins [IMSoP]