| Subject: | Quotes used in Apache style Include Directives |
If an Include directive has a Configuration filename with quotes around
it, Config::General cannot find it and dies. Using the same include
line, removing the quotes works.
For example:
Include "conf/more-parameters.conf" <--- Doesn't work
Include conf/more-parameters.conf <--- Works
This occurs with -ApacheCompatible turned on. In a typical Unix setup,
most people do not put quotes around the filename, but I believe the
Apache configuration will allow it. In Windows (or Unix), it may be
required to accommodate spaces in the filename.
I understand the module shouldn't remove quotes from values and it's up
to me to handle other values with quotes; however, the include
processing is automatic during the initial parsing and a show stopper
under this condition.
I use Config::General to retrieve information on Apache configurations
and cannot change the Apache configuration files. I posted this to the
forum; however, I do not know if the forum is monitored (only 2 old
posts were there.)
uname -a
Linux vincent 2.6.22-15-generic #1 SMP Fri Jul 11 19:25:33 UTC 2008 i686
GNU/Linux
perl -v
This is perl, v5.8.8 built for i486-linux-gnu-thread-multi
Config::General v2.40