Loading ...
Sorry, an error occurred while loading the content.

RE: index.pl not default, even when specified

Expand Messages
  • Adam Prime x443
    I think it s worth noting (again) that as Perrin said, if you use a instead of a for your registry scripts, then
    Message 1 of 25 , Sep 30, 2005
    • 0 Attachment
      I think it's worth noting (again) that as Perrin said, if you use a <filesmatch *.pl> instead of a <directory /whatever> for your registry scripts, then mod_dir will still handle the directory indexes correctly. If you want a quick fix, it's probably not going to get any quicker than that.

      Adam


      -----Original Message-----
      From: Geoffrey Young [mailto:geoff@...]
      Sent: Friday, September 30, 2005 12:44 PM
      To: Philip M. Gollucci
      Cc: Jonathan Steffan; Perrin Harkins; Dickon Newman;
      modperl@...
      Subject: Re: index.pl not default, even when specified




      Philip M. Gollucci wrote:
      > Geoffrey Young wrote:
      >
      >> if you read through the above thread completely you'll see an analysis of
      >> what happens when using SetHandler + DirectoryIndex - basically,
      >> mod_dir is
      >> never able to apply the DirectoryIndex directive because it never
      >> enters the
      >> request. however, it is possible to get DirectoryIndex working
      >> without the
      >> PerlFixupHandler in that thread...
      >
      > Is there anthing on perl.apache.org in docs about this?

      patches welcome :)

      --Geoff
    Your message has been successfully submitted and would be delivered to recipients shortly.