View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0020865 | mantisbt | bugtracker | public | 2016-04-30 12:26 | 2021-08-07 08:26 |
| Reporter | dregad | Assigned To | dregad | ||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 1.3.0-beta.1 | ||||
| Target Version | 1.3.0-rc.2 | Fixed in Version | 1.3.0-rc.2 | ||
| Summary | 0020865: 'Content Encoding Error' when errors occur before compress handler is started | ||||
| Description | If a run-time error is triggered while initializing the Core (e.g. a PHP deprecated warning, ), the browser displays a 'Content Encoding Error' instead of showing the actual error, which is confusing and makes troubleshooting more difficult than it should be. I noticed this while testing the behavior described in 0020864 on 1.3.x branch. | ||||
| Steps To Reproduce | To reproduce the error add some code that triggers a PHP notice or some other error, e.g. $t = test;in user_pref_api.php | ||||
| Tags | No tags attached. | ||||