| Summary | Config Backup Files (all applications) |
| Queue | Horde Base |
| Queue Version | HEAD |
| Type | Enhancement |
| State | Resolved |
| Priority | 1. Low |
| Owners | Chuck Hagenbuch <chuck (at) horde (dot) org> |
| Requester | rdorfner (at) sysdesign-edv (dot) de |
| Created | 02/28/2008 (71 days ago) |
| Due | |
| Updated | 02/28/2008 (71 days ago) |
| Assigned | 02/28/2008 (71 days ago) |
| Resolved | 02/28/2008 (71 days ago) |
| Attachments | |
| Milestone | |
| Patch |
State ⇒ Resolved
Done.State ⇒ Assigned
Assigned to Chuck Hagenbuch
Makes sense to me.Queue ⇒ Horde Base
Summary ⇒ Config Backup Files (all applications)
Type ⇒ Enhancement
Priority ⇒ 1. Low
State ⇒ New
It's dangerously to create a backup files called conf.php.bak after configuration in a horde application has been changed. A general webserver will deliver the backup file (e.g. http://myserver.com/hordedir/config/config.php.bak) without any restrictions like htaccess etc.
It would be better to name the files conf.bak.php to avoid this.