Adding Directives At Runtime

[Christopher H. Laco]

Are there any phase or scope limitations when adding directives to apache at runtime? I've never done it, but I'm looking into a hack that would require it.

        <Perl>
            use lib qw(/var/www/MyCatalystApp/lib);
        </Perl>
        # ideally, here would be when the Catalyst app adds known
        # additional Location directives
        PerlModule MyCatalystApp

        <Location />
            SetHandler perl-script
            PerlHandler MyCatalystApp
        </Location>







Thanks,
-=Chris

The scenerio. In a Catalyst based app, Catalyst is setup to handle all requests; be they for dynamic urls, or for physical files with static content. There are various plugins and httpd.conf changes that can be made to disuade this behaviour, but I would like to take it a step further and make it Just Work(TM) so I don't have to tweak the httpd.conf or the static plugin every time I add a new static directory. At the time the Catalyst app loads, it knows all of the urls (<Location>) that it should handle. I think everything else should just be a regular Apache request without the need of adding LocationMatch or Alias directives manually in httpd.conf. So, given a list of urls, is it possible to dynamically add <Location /somemethod> tags to Apache? I think so, I just don't know where to start.

smime.p7s
Description: S/MIME Cryptographic Signature