Turns out the solution to my problem was quite simple. I replaced:
DataSources Environment
with:
DataSources Environment
and all of my problems resolved. I am no longer using any
PerlTransHandler or PerlFixupHandler (as described in other emails),
just DirectoryIndex a
Geoffrey Young wrote:
My PerlResponseHandler works fine on files in the /tools directory for
pages that are specified, for example:
/tools/environment.page
/tools/index.page
If I use just the directory URI:
/tools/
the DirectoryIndex specification works but I don't get any configuration
data
> My PerlResponseHandler works fine on files in the /tools directory for
> pages that are specified, for example:
>
> /tools/environment.page
> /tools/index.page
>
> If I use just the directory URI:
>
> /tools/
>
> the DirectoryIndex specification works but I don't get any configuration
> data
I define a generalized output filter for any .page file:
SetHandler perl-script
PerlOutputFilterHandler Layout
I have a block:
DataSources Environment
which I'm referencing via an Alias from a VirtualHost:
ServerName home.Dimension.org
Docu
