Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Message-ID: <3C5F6B34.7010400@stason.org>
Date: Tue, 05 Feb 2002 13:18:44 +0800
From: Stas Bekman <stas@stason.org>
Organization: Hope, Humanized
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.7) Gecko/20011221
MIME-Version: 1.0
To: dev@httpd.apache.org
Subject: Re: more minor 2.0.31 breakage
References: <3C5ECA61.CD03A261@remulak.net> <3C5EE42C.9958AB32@Golux.Com>
 <3C5F45CB.8050901@stason.org> <01d901c1adf6$7ab50bd0$95c0b0d0@v505>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

William A. Rowe, Jr. wrote:

> From: "Stas Bekman" <stas@stason.org>
> Sent: Monday, February 04, 2002 8:39 PM
> 
> 
> 
>>Rodent of Unusual Size wrote:
>>
>>
>>>Greg Ames wrote:
>>>
>>>
>>>>I just noticed that autoindex listings from apache.org no
>>>>longer display the folder icon for directories.  You see
>>>>a '?' icon instead.  The Rodent tells me there's some kind
>>>>of magic type that mod_autoindex uses to figure this out.
>>>>Not debugged yet.
>>>>
>>>>
>>>As an unsubstantiated WAG, I would guess that the subrequest
>>>that's sent off to determine the content-type is running
>>>afoul of mod_dir somehow, and S_ISDIR isn't set correctly
>>>when it comes back.
>>>
>>
>>BTW, since you are talkinga about mod_autoindex, I don't recall that it 
>>was working this way before:
>>
>>I've uploaded a dir with files to apache.org/~stas/. as of that moment 
>>apache.org was running 2.0.28. I was trying to view apache.org/~stas/, 
>>all the files/dirs showed up, but not this new sub-dir. When I've tried 
>>to enter the new directory manually 
>>http://apache.org/~stas/modperl-site/ I've got 500 error. Looking at 
>>error_log revealed that I had a broken .htaccess in that directory. I 
>>don't understand why mod_autoindex won't display the directory in the 
>>index's listing.
>>
>>I think it's a bug. The sub-directory can be password-protected. Does it 
>>mean that mod_autoindex won't display it, since it'll fail to run the 
>>sub-request?
>>
> 
> By design, for better or worse [feel free to debate here.]
> 
> The new logic [perhaps 1.3 as well, you would have to look] does a subrequest 
> on the /~stas/ url ... and decides it's broken [or inaccessable, or whatever] 
> and autoindex won't display it.  What's broken about not displaying things that
> the user cannot access?

I gave an example of a password protected sub-directory. You say that 
it's correct not to display it then? How do you know whether the user 
cannot access this directory? May be he does have the needed access 
credentials.

-- 


_____________________________________________________________________
Stas Bekman             JAm_pH      --   Just Another mod_perl Hacker
http://stason.org/      mod_perl Guide   http://perl.apache.org/guide
mailto:stas@stason.org  http://ticketmaster.com http://apacheweek.com
http://singlesheaven.com http://perl.apache.org http://perlmonth.com/