=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex">Presently, Apache::ReadConfig doesn't =
seem to provide a way to represent

the order of directives, which limits its usefulness when used with

modules like mod_rewrite that rely on the order of certain directives:



<VirtualHost "*:80">

=C2=A0 =C2=A0 ServerName target=3D"_blank">example.com

=C2=A0 =C2=A0 DirectoryRoot /www

=C2=A0 =C2=A0 <Directory "/www">

=C2=A0 =C2=A0 =C2=A0 =C2=A0 RewriteEngine On

=C2=A0 =C2=A0 =C2=A0 =C2=A0 RewriteCond %{REQUEST_FILENAME} !-f

=C2=A0 =C2=A0 =C2=A0 =C2=A0 RewriteCond %{REQUEST_FILENAME} !-d

=C2=A0 =C2=A0 =C2=A0 =C2=A0 RewriteRule (.*) cgit.cgi/$1 [END,QSA]

=C2=A0 =C2=A0 </Directory>

</VirtualHost>



This piece of configuration is (AFAIK?) impossible to create using

Apache::ReadConfig, because %VirtualHost and %Directory are unordered

hashes.



Assuming I'm correct about the problem, what could be done to fix it?r>


My personal idea is to create an additional module created

Apache::ReadConfig::Full (or something), which allows the following:



$Config->push(['VirtualHost', '*:80'] =3D> block(

=C2=A0 =C2=A0 ServerName =3D> '"noreferrer" target=3D"_blank">example.com',

=C2=A0 =C2=A0 DirectoryRoot =3D> '/www',

=C2=A0 =C2=A0 =C2=A0 =C2=A0 ['Directory', '/www'] =3D> b=
lock(

=C2=A0 =C2=A0 =C2=A0 =C2=A0 RewriteEngine =3D> On,

=C2=A0 =C2=A0 =C2=A0 =C2=A0 RewriteCond =3D> '%{REQUEST_FILENAME} !-=
f',

=C2=A0 =C2=A0 =C2=A0 =C2=A0 RewriteCond =3D> '%{REQUEST_FILENAME} !-=
d',

=C2=A0 =C2=A0 =C2=A0 =C2=A0 RewriteRule =3D> '(.*) cgit.cgi/$1 [END,=
QSA]'

=C2=A0 =C2=A0 )

);



The `block' function creates an object that amounts to an ordered,

multi-value hash a la Hash::MultiValue. (The global $Config variable is

the same type of object.)



Before I start looking into the possibility of creating such an

interface, I thought I'd ask here whether my assumptions about

Apache::ReadConfig's limitations are correct.



Best regards

John