View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 440 | Exception_DefaultHandler | All | public | 7 Sep 2017 14:55 | 1 Jun 2018 19:29 |
| Reporter | timj | Assigned To | timj | ||
| Priority | normal | Severity | feature | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Product Version | 1.0.1 | ||||
| Target Version | 1.0.2 | Fixed in Version | 1.0.2 | ||
| Summary | 440: Truncate excessively long PHP error details | ||||
| Description | Sometimes PHP error details can be of excessive length (for example, if they contain a complete SQL query with binary data embedded). It would make sense to truncate excessively long PHP error details, for sanity. (By default, at a length well under max_email_size). Note this is not the same issue as 436, although they can both be triggered in similar circumstances. | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 7 Sep 2017 14:55 | timj | New Issue | |
| 7 Sep 2017 14:55 | timj | Status | new => assigned |
| 7 Sep 2017 14:55 | timj | Assigned To | => timj |
| 7 Sep 2017 14:58 | timj | Severity | minor => feature |
| 7 Sep 2017 23:04 | timj | Status | assigned => resolved |
| 7 Sep 2017 23:04 | timj | Resolution | open => fixed |
| 7 Sep 2017 23:04 | timj | Fixed in Version | => 1.0.2 |
| 7 Sep 2017 23:04 | timj | Note Added: 497 | |
| 1 Jun 2018 19:29 | timj | Status | resolved => closed |