Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <3CD67075.27EFF646@wapme-systems.de> Date: Mon, 06 May 2002 14:00:53 +0200 From: Stipe Tolj Organization: Wapme Systems AG X-Accept-Language: de MIME-Version: 1.0 To: "Gerrit P. Haase" CC: cygwin AT cygwin DOT com Subject: Re: Apache mod_autoindex.c buggy? References: <73389842644 DOT 20020416215027 AT familiehaase DOT de> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit "Gerrit P. Haase" wrote: > > I'm using the Cygwin Apache several days now. > I think the mod_autoindex.c module is buggy. > > I have loaded the module and in the httpd.conf section > about fancyindexing icons where the icons are assigned > to the files according to their suffixes I have the > default setting like: > AddIcon /icons/c.gif .c > However, a C file isn't displayed with its icon > but with the default text icon. > (E.g.: http://62.138.63.18/cywgin/impgen/ ) > See also the core in this dir which should show a bomb: > AddIcon /icons/bomb.gif core > > I looked in the /icons dir and the c.gif is correct (bomb too;). > If I change other entries it works ok. (like adding .bz2 to > the compressed files list). > > Strange! that's definitly strange in my point of view. Can you pass me the httpd.conf file to have a peak on that. Stipe tolj AT wapme-systems DOT de ------------------------------------------------------------------- Wapme Systems AG Münsterstr. 248 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: info AT wapme-systems DOT de Internet: http://www.wapme-systems.de ------------------------------------------------------------------- wapme.net - wherever you are -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/