Bug 39923

Summary:	AddDescription doesn't work in server config with a URI-path (or Filesystem path)
Product:	Apache httpd-2	Reporter:	Vincent Jong <vjong>
Component:	mod_autoindex	Assignee:	Apache HTTPD Bugs Mailing List <bugs>
Status:	RESOLVED LATER
Severity:	normal	Keywords:	MassUpdate
Priority:	P2
Version:	2.2.2
Target Milestone:	---
Hardware:	PC
OS:	Linux

Description Vincent Jong 2006-06-28 17:48:20 UTC

Working with rbowen on #apache on freenode, I've tried a variety of ways with
AddDescription in conf/extra/httpd-autoindex.conf - using the uri-path reletive
to the document root and using the full system file path. Using either of these,
fails to put the description on the corresponding file.

Ex.
AddDescription "adobe logo." /stuff/MiscImages/adobelogo.png

AddDescription "adobe logo." /var/www/stuff/MiscImages/adobelogo.png

What does work is to just use the filename.

Ex.

AddDescription "adobe logo." adobelogo.png

There is only one example in the 2.2 docs regarding this and it is ambiguous as
to whether the file in question is a URI-path or a full system file path.

Doc Example.

 AddDescription "The planet Mars" /web/pics/mars.gif

Either this is a documentation issue or AddDescription doesn't work with paths.

Comment 1 Ferenc Veres 2010-03-15 22:50:38 UTC

This works for me, I don't know why...

ddDescription "adobe logo." stuff/MiscImages/adobelogo.png

Tested in Directory section and .htaccess, Apache 2.2.

Comment 2 Ferenc Veres 2010-03-15 22:51:53 UTC

Copy paste error, sorry. (The fix is the slash, not the "A")

AddDescription "adobe logo." stuff/MiscImages/adobelogo.png

Comment 3 Eric Covener 2011-11-21 00:41:01 UTC

sigh, different bug then I thought

Comment 4 Eric Covener 2011-11-21 01:05:26 UTC

seemed busted to me and fixed in r1204307

Comment 5 Eric Covener 2011-11-21 05:16:44 UTC

reverted, needs closer look

Comment 6 William A. Rowe Jr. 2018-11-07 21:09:48 UTC

Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd.

As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd.

If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question.

If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with.

Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.