Bug 46454 - escaping wildcards in AddIcon filename matching
Summary: escaping wildcards in AddIcon filename matching
Status: RESOLVED LATER
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_autoindex (show other bugs)
Version: 2.2.11
Hardware: PC Linux
: P2 minor (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords: MassUpdate
Depends on:
Blocks:
 
Reported: 2008-12-30 19:47 UTC by Jan Newmarch
Modified: 2018-11-07 21:08 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Newmarch 2008-12-30 19:47:24 UTC
I have a filename with some question marks in it e.g. "ab?cd". In AddIcon from mod_autoindex no match is possible with that filename e.g.

    AddIcon image.xbm "ab?cd"

fails. Inspection of mod_autoindex.c (2.2.11) line 259, add_icon calls push_item. push_item on line 202 calls ap_is_matchexp, which just checks for the presence of '?' or '*' in the filename and then does a pattern match for '*'. It doesn't seem possible to get an icon for a filename with a '*' or '?' in it.

Possible fix: change ap_is_matchexp to return true for ENESCAPED * or ? and false if there are none or they are escaped as in "ab\?cd"

Workaround: change the filename :-(

Environment : Linux 2.6.24
Comment 1 William A. Rowe Jr. 2018-11-07 21:08:59 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.