Greetings and Salutations, ( I apologize ahead of time if this has already been beaten to death or makes no sense. It's late/early)
Versions: AxKit 1.62, with apache 1.3.28 and mod_perl 1.3.28 1.62 possibly has a bug, or just my mis-understanding in Provider/AxKit.pm. Whenever I call http://my.website.edu/dir[/] the page just keeps looping until either I or the websever gives up with a resulting url that looks like: http://my.website.edu/dir////////////// . I tried the AxHandleDir settings but that either gave me the url above or XML contents but not what I was looking for which is the file set by "DirectoryIndex". I downgraded to 1.6.1 with the same configuration that produces the "...//////..." urls in 1.6.2 and 1.6.1 works fine. After some digging (in 1.6.2) I found that the decline function in Provider/File.pm returns a redirect to the browser if the URL is a directory, regardless of why it was declined by AxKit. I believe this redirect should only happen if AxHandleDirs is on (which would only decline it if it doesn't have a trailing slash). To test my theory (after reinstalling 1.6.2) I changed the decline function from: sub decline { my $self = shift; if ($self->_is_dir) { $self->{apache}->header_out('Location' => $self->{apache}->uri . "/"); return 302; } } TO: sub decline { my $self = shift; if ($self->_is_dir) { if ($AxKit::Cfg->HandleDirs()) { $self->{apache}->header_out('Location' => $self->{apache}->uri . "/"); return 302; } } } With this change AxHandleDirs works correctly both on and off, without producing the "..////..." urls. At first glance does this look like it will break anything else? I don't think it will but then again, I don't know and/or understand all the inner workings of AxKit. Damion --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
