Bug #1286 for Apache-FileManager: Location cannot have same name as directory.

Mon Jul 15 23:47:17 2002 Guest - Ticket created

Subject:

Location cannot have same name as directory.

I don't know if this is a bug or a feature, but it's not documented. Given: <Location /FileManager> SetHandler perl-script PerlHandler Apache::FileManager PerlSetVar DOCUMENT_ROOT /home/htdocs/filemanager </Location> and the specified directory exists, you will get a standard generated index instead of the generated file manager page. Case doesn't seem to matter.

Wed Jul 17 18:43:30 2002 pmc2 [...] blackstar.sr.unh.edu - Correspondence added

Date:	Wed, 17 Jul 2002 18:43:22 -0400 (EDT)
From:	Phil Collins <pmc2 [...] blackstar.sr.unh.edu>
To:	Guest via RT <bug-Apache-FileManager [...] rt.cpan.org>
Subject:	Re: [cpan #1286] Location cannot have same name as directory.

I'm not sure why this isn't working for you. You are using an older version. I've attached the latest version. This version also should be up on cpan tomorrow. Let me know the outcome. Phil On Mon, 15 Jul 2002, Guest via RT wrote: Show quoted text

> > > This message about Apache-FileManager was sent to you by guest via rt.cpan.org > > Full context and any attached attachments can be found at: > <URL: https://rt.cpan.org/Ticket/Display.html?id=1286 > > > I don't know if this is a bug or a feature, but it's not documented. > > Given: > > <Location /FileManager> > SetHandler perl-script > PerlHandler Apache::FileManager > PerlSetVar DOCUMENT_ROOT /home/htdocs/filemanager > </Location> > > and the specified directory exists, you will get a standard generated index instead of the generated file manager page. Case doesn't seem to matter. >

-- *********************************************************** Philip Collins email: pmc2@sr.unh.edu Web/Database Programmer phone: (603) 862-7038 UNH Research Computing Center office: Morse Hall Room 209 ***********************************************************

Download Apache-FileManager-0.16.tar.gz
application/x-gzip 10.4k

Message body not shown because it is not plain text.

Thu Jul 18 17:13:32 2002 Guest - Correspondence added

From:

harleypig [...] harleypig.com

[pmc2@blackstar.sr.unh.edu - Wed Jul 17 18:43:30 2002]: Show quoted text

> I'm not sure why this isn't working for you. You are using an older > version. I've attached the latest version. This version also should > be up on cpan tomorrow. Let me know the outcome.

Well, here's a *little* more information: when I tried to make it publicly accessible for you to look at I ran into some wierd issues. <Location /demo_filemanager> SetHandler perl-script PerlHandler Apache::FileManager PerlSetVar DOCUMENT_ROOT /home/htdocs/filemanager_demo Satisfy any </Location> works fine, but <Location /BadFileManager> SetHandler perl-script PerlHandler Apache::FileManager PerlSetVar DOCUMENT_ROOT /home/htdocs/badfilemanager Satisfy any </Location> forces username/password entry. The root location is using BasicAuth and require valid-user ... but I don't understand why this would make any difference. Maybe I'm just doing something really screwy.

Fri Jul 19 09:21:52 2002 pmc2 [...] blackstar.sr.unh.edu - Correspondence added

Date:	Fri, 19 Jul 2002 09:21:49 -0400 (EDT)
From:	Phil Collins <pmc2 [...] blackstar.sr.unh.edu>
To:	Guest via RT <bug-Apache-FileManager [...] rt.cpan.org>
Subject:	Re: [cpan #1286] Location cannot have same name as directory.

Show quoted text

> Well, here's a *little* more information: when I tried to make it > publicly accessible for you to look at I ran into some wierd issues. > > <Location /demo_filemanager> > SetHandler perl-script > PerlHandler Apache::FileManager > PerlSetVar DOCUMENT_ROOT /home/htdocs/filemanager_demo > Satisfy any > </Location> > > works fine, but > > <Location /BadFileManager> > SetHandler perl-script > PerlHandler Apache::FileManager > PerlSetVar DOCUMENT_ROOT /home/htdocs/badfilemanager > Satisfy any > </Location> >

Show quoted text

> forces username/password entry. The root location is using BasicAuth > and require valid-user ... but I don't understand why this would make > any difference.

This is something Apache related. Apache::FileManager only comes into play during the Content handlingg phase (before authorization and authentication phases). Try putting Satify All and see what happens. I know this isn't the correct solution, but the results would be interesting. I'm thinking the "Satisfy Any" isn't being set for the /BadFileManager location directive. Phil -- *********************************************************** Philip Collins email: pmc2@sr.unh.edu Web/Database Programmer phone: (603) 862-7038 UNH Research Computing Center office: Morse Hall Room 209 ***********************************************************

Fri Jul 19 15:37:07 2002 Guest - Correspondence added

From:

harleypig [...] harleypig.com

[pmc2@blackstar.sr.unh.edu - Fri Jul 19 09:21:52 2002]: Show quoted text

> This is something Apache related. Apache::FileManager only comes into > play during the Content handlingg phase (before authorization and > authentication phases). Try putting Satify All and see what happens. I > know this isn't the correct solution, but the results would be > interesting. I'm thinking the "Satisfy Any" isn't being set for the > /BadFileManager location directive.

'Satisfy all' made no difference. Additionally, give the following configuration: <Location /demo_filemanager> SetHandler perl-script PerlHandler Apache::FileManager PerlSetVar DOCUMENT_ROOT /home/htdocs/filemanager_demo Satisfy any </Location> if I go to /filemanager_demo I get the auto_index generated page. I realize this is normal, but it might be a problem people run into later. I haven't tried setting Location to deny all for the specific directory, but I don't really want to ... I'd like to just be able to say "this directory is being handled this way". I'm not sure if this is a module or apache issue. NOTE: If you create a symbolic link in the document root, FileManager will follow it. Furthermore, if you delete the link, FileManager will display the root directory.