Bug 1196553

Summary:	bomb.gif icon displayed with other files than intended
Product:	Red Hat Software Collections	Reporter:	Martin Frodl <mfrodl>
Component:	httpd	Assignee:	Jan Kaluža <jkaluza>
Status:	CLOSED ERRATA	QA Contact:	Martin Frodl <mfrodl>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	httpd24	CC:	optak, qe-baseos-apps
Target Milestone:	rc
Target Release:	2.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	httpd24-httpd-2.4.18-1.el6 httpd24-httpd-2.4.18-1.el7	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1196325	Environment:
Last Closed:	2016-05-31 10:15:53 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1170215, 1196325, 2017143, 2075406, 2077039
Bug Blocks:

Description Martin Frodl 2015-02-26 09:27:45 UTC

+++ This bug was initially created as a clone of Bug #1196325 +++

Description of problem:

The default /opt/rh/httpd24/root/etc/httpd/conf.d/autoindex.conf file contains the following line:

  AddIcon /icons/bomb.gif core.

As far as understand it, there are at least two issues with this syntax. First, the bomb icon is not displayed where it probably should. Second, in certain cases the bomb icon is displayed where it should not.

Judging from what I see in a directory listing in my browser, the directive tells Apache to use the bomb icon with all files *ending in* "core.", e.g. "core.", "score", "hardcore." et al. Contrarily, the icon will not be displayed with files "core.10216", "core.httpd.12344" and their likes, which is what it was probably meant for (correct me if I am wrong).

After a little fiddling, this is what got me closest to the expected behaviour:

  AddIcon /icons/bomb.gif */core.*


Version-Release number of selected component (if applicable):
httpd24-httpd-2.4.12-4.el7.x86_64

Comment 6 errata-xmlrpc 2016-05-31 10:15:53 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2016:1154