"httpd -t" states an error if environment variables (origin often /etc/apache2/envvars) are used with the directives User or Group. This results in Quest6 failing.
Is this a bug? Or is it a feature?
For now we should enforce that these environment variables are pulled into the configuration. Running multiple apache servers is still possible with multiple configuration files. But on the other hand one has to look into the very individual startup process of the apache to ensure that the variables get set. So this makes it easier for both, our development and the administration of the startup process of the apache (cause you don't need to bother envvars).
But the program should get more verbosely about that problem, not only in the html report.
"httpd -t" states an error if environment variables (origin often /etc/apache2/envvars) are used with the directives User or Group. This results in Quest6 failing. Is this a bug? Or is it a feature?
For now we should enforce that these environment variables are pulled into the configuration. Running multiple apache servers is still possible with multiple configuration files. But on the other hand one has to look into the very individual startup process of the apache to ensure that the variables get set. So this makes it easier for both, our development and the administration of the startup process of the apache (cause you don't need to bother envvars).
But the program should get more verbosely about that problem, not only in the html report.