Marilyn Burgess wrote:
> Hello,
>
> I'm running modperl2 on Debian from the libapache2-mod-perl2 debian package
> and I can't get the DirectoryIndex rule to work properly. I have the line
>
> DirectoryIndex index.html index.cgi index.pl index.php index.xhtml
>
Hello,
I'm running modperl2 on Debian from the libapache2-mod-perl2 debian package
and I can't get the DirectoryIndex rule to work properly. I have the line
DirectoryIndex index.html index.cgi index.pl index.php index.xhtml
in apache2.conf, and in the file default in sites-available
Marc M. Adkins wrote:
> I have been struggling with DirectoryIndex behavior and configuration
> information from custom Perl directives for a while now. I've been
> scanning the web and posting here and thanks for the previous responses.
>
> I now have a solution that se
wrote:
On Sat, 07 Jul 2007 11:13:49 -0700
"Marc M. Adkins" <[EMAIL PROTECTED]> wrote:
I have been struggling with DirectoryIndex behavior and configuration
information from custom Perl directives for a while now. I've been
scanning the web and posting here and thanks for th
On Sat, 07 Jul 2007 11:13:49 -0700
"Marc M. Adkins" <[EMAIL PROTECTED]> wrote:
> I have been struggling with DirectoryIndex behavior and configuration
> information from custom Perl directives for a while now. I've been
> scanning the web and posting he
I have been struggling with DirectoryIndex behavior and configuration
information from custom Perl directives for a while now. I've been
scanning the web and posting here and thanks for the previous responses.
I now have a solution that seems to work. I have extracted a minimal
set of
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
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
> 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
n.org
DocumentRoot${WEB_07_ROOT}/dimension
DirectoryIndex index.page
Alias /tools ${WEB_07_ROOT}/tools
SetHandler perl-script
PerlResponseHandler Data
(never mind the macro expansion strings, I'm pre-processing the
configur
I think that this is pretty import to add to the core features. I was
able to get the patch to work, but I had to add:
use Apache2::RequestUtil;
> **
> mod_perl-1.99_16-3
> **
> DirectoryIndex index.pl
please see this thread
http://marc.theaims
--- Geoffrey Young <[EMAIL PROTECTED]> wrote:
> this needs to be fixed. those constants are
explicitly exported in
> Fixup.pm, so if you're getting those warnings
> something is wrong. the
> pragmata you commented out is there for your
> protection - if you need to
> comment it out something else
> My/Fixup.pm package exactly as
> http://marc.theaimsgroup.com/?l=apache-modperl&m=111445150218566&w=2
>
> Note 1:
> - All references to Apache2 changed to Apache (fresh
> install of Fedora Core 3 & one up2date
> (httpd is 2.0.52 and mp2 is 1.99_16-3)
> - no complaints
>
> Problem 1:
>
--- Geoffrey Young <[EMAIL PROTECTED]> wrote:
> since you're new to mod_perl it's probably not
> obvious from that thread what
> the solution is.
>
>
>
http://marc.theaimsgroup.com/?l=apache-modperl&m=111445150218566&w=2
>
> the code at the bottom of that link (My::Fixup)
> needs to be enabled
Thomas Hilbig wrote:
> I really apologize for resurrecting a thread that was
> put to rest almost a month ago. I am just running
> into this problem now, and I don't quite understand
> what the fix is. I'm very new to writing a MP
> handler.
since you're new to mod_perl it's probably not obvio
I really apologize for resurrecting a thread that was
put to rest almost a month ago. I am just running
into this problem now, and I don't quite understand
what the fix is. I'm very new to writing a MP
handler.
I am trying to write a (yet another) authentication
handler for a directory that is t
for the sake of the archives, william reported that the below fixup handler
is "working like a champ" so I guess this is a workable solution for anyone
in the same situation.
and for anyone listening, rolling up a test tarball like william did was
outstanding - I was more than happy (ecstatic, ac
ur last test
> is wrong - your DirectoryIndex puts the index script ahead of everything
> else, so the results should match "Hello" and not "welcome".
Indeed you are correct about the bad test. I've incorporated the new
fixup handler into my production config and i
>>SetHandler is forcing the handler to be mod_perl, but really mod_dir needs
>>to step in and handle the / -> DirectoryIndex conversion. so... what I would
>>do is alter that fixup handler to do something like this
>>
>> if ($r->handler('perl-script&#
ong in my settings, but as I've reported
before, these used to work under mp1.
> SetHandler is forcing the handler to be mod_perl, but really mod_dir needs
> to step in and handle the / -> DirectoryIndex conversion. so... what I would
> do is alter that fixup handler to do so
he module; he had no further
> suggestions so I did some further debugging. It turns out that I'm not
> having a problem with appending a trailing slash; Apache seems to be
> doing this just fine with or without the Apache::Dir module.
>
> The problem I'm having is that A
t I'm not
having a problem with appending a trailing slash; Apache seems to be
doing this just fine with or without the Apache::Dir module.
The problem I'm having is that Apache is not setting the DirectoryIndex
to a valid filename. It is instead complaining that it's trying to se
On Tue, Apr 12, 2005 at 08:33:59PM -0400, Geoffrey Young wrote:
> yes, because mp1 is configured to handle requests of type DIR_MAGIC_TYPE
> whereas mp2 is not. this is a bug or a feature, depending on whether you
> think mp1 was correct or not :)
OK, that makes sense. I was beginning to worry ab
dex) or disable
> perl-handler, Apache is correctly serving the index file. Any ideas on
> why Apache would appear to be ignoring my DirectoryIndex setting?
yup :)
> This configuration had been working under mp1.
yes, because mp1 is configured to handle requests of type DIR_MAGIC_TY
as on
why Apache would appear to be ignoring my DirectoryIndex setting?
Here's the relevant part of my httpd.conf:
AllowOverride None
Options ExecCGI MultiViews -Indexes SymLinksIfOwnerMatch IncludesNoExec
DirectoryIndex index login index.html
# default handler is perl-script
Perl
I've been trying to track down why the DirectoryIndex under Apache2+MP2
isn't working with the following configuration. From Google and
listserv searching, the only suggestion I found was to add a
"RedirectMatch permanent (.*)/$ $1/index.html" to my config, but this
does
26 matches
Mail list logo
