[PLUG] Apache and mod_perl configuration

[Daniel Hedlund]

Roderick,

Is the reason that you can access some static files because you have 
your server set up to intercept all requests within certain directories 
to be processed by mod_perl or such?

You might like to have a look into Catalyst::Plugin::Static::Simple to 
see if it will fix your problems:
http://search.cpan.org/dist/Catalyst-Plugin-Static-Simple/

Catalyst::Plugin::Static::Simple README:
http://search.cpan.org/src/MRAMBERG/Catalyst-Plugin-Static-Simple-0.14/README

Daniel Hedlund
daniel at digitree.org


Roderick A. Anderson wrote:
> My adventure has me at "wit's end" ( whit's end?  Been too many years. )
> 
> I'm working on a application that use Catalyst and it is set up to use 
> mod_perl.
> 
> The problem I've run into is I can't get past mod_perl when accessing 
> static files ... *.js *.css with out placing the whole path in the XHTML.
> 
> For those not familiar with Catalyst the standard 
> installation/configuration places javascript, css, and ( static ) html 
> files directories in [/var/www/]root/static/.
> 
> The only way I've been able to get to them is to use the full path from 
> DocumentRoot.
> 
> DocumentRoot is set to /var/www/root/
> 
> But even with Aliases I have to use /static/css/site.css or 
> /static/js/site.js
> 
> I've tried reordering the declaration in httpd.conf, going from 
> <Directory> to <Location>, with and without trailing slashes; finally 
> arriving at wit's end.  ( The dragon looks pretty simple right now. )
> 
> All the documentation I've found for mod_perl helps with over-riding the 
> Apache default handlers but nothing on circumventing mod_perl -- which 
> is suppose to be the "default" behavior.  Go figure, eh?
> 
> Any suggestions, examples, clue-sticks?
> 
> 
> Thanks,
> Rod