Bug#714083: default-ssl.conf should also be prefixed with 000- to be sure to be first ssl virtualhost
Control: retitle -1 default-ssl.conf should also be prefixed with 000- to be sure to be first ssl virtualhost
Control: severity -1 normal
Control: tags -1 help
Increased severity because this does easily cause problems, unexpected behaviour, confusion, and support requests when an ssl vhost is put in a config with a filename that is sorted before 'default-ssl.conf', e.g. 'custom-vhost.conf' or 'a-vhost.conf'.
There is already a pull request [1] that was already merged but then reverted because changing this config file’s name is not trivial and I had not thought of how to do this migration on productive systems.
Concrete questions are:
* how to deal with this on all variations of systems
** unchanged, not activated (will dpkg/ucf/whatever-handles-these-config-files do the right thing? I guess the old file will be removed and the new file placed, but how to be certain?)
** changed, not activated (what do we do? move the existing file? remove it, install the new?)
** unchanged, activated (similar to first variant, but how to deal with the symlink in sites-enabled/?)
** changed, activated (do we even do anything in this case or just assume that it’s working as intended and leave the admin to it?)
Concrete suggestions, patches, references to relevant docs, merge requests, etc. welcome!
Cheers
henk
Reply to: