Ticket #413 (defect)
Opened 3 years ago
Last modified 3 years ago
Improve configuration error behavior
Status: closed (fixed)
| Reported by: | dowski | Assigned to: | rdelon |
|---|---|---|---|
| Priority: | normal | Milestone: | 2.2-beta |
| Component: | CherryPy code | Keywords: | |
| Cc: |
I think that CP should provide better handling of errors in the config. My initial thoughts on this were posted to the cp-devel list.
Going with Robert's suggestion in that thread, I think that CP should notify the user on startup if there are serious enough errors in the config and then halt execution.
Change History
12/29/05 18:06:21: Modified by fumanchu
- status changed from new to closed.
- resolution set to fixed.
Fixed in [897]. Well, the original request (staticfilter.on = True without corresponding .file, .dir or .match) isn't implemented, since one might want to turn it on in one dir and only provide the .file, .dir, or.match in subdirs. However, there's an initial test to verify that the value of "server.environment" is present in the config.environments dict. There's a new "check_config" method in _cpserver, to which we can add future config tests on startup.