You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by David Harris <dh...@drh.net> on 1999/08/17 02:23:34 UTC
[patch] remove wildcard handler warning
Anytime a wildcard handler is invoked, a warning is written to the error_log
file.
For example, this configuration (even though it works perfectly as intended):
AddHandler x-script-info .info-set
Action x-script-info /cgi-bin/set/tr3TR-info
causes this warning:
[Mon Aug 16 20:12:26 1999] [warn] [client 192.168.0.5] handler
"x-script-info" not found for: /web/f/e/feline/home/whatever.info-set
So, I worked around the warning by using this configuration:
AddType handler/x-script-info .info-set
Action handler/x-script-info /cgi-bin/set/tr3TR-info
IMHO, this warning is fickle. From what I understand wildcard handlers are
perfectly allowed and are not considered "bad API practice". I've appended a
patch to remove this warning.
PS, I don't know where you are in the release cycle at the moment. Hope I'm not
interfering.
- David Harris
Principal Engineer, DRH Internet Services
--- src/main/http_config.c.orig Mon Aug 16 20:23:16 1999
+++ src/main/http_config.c Mon Aug 16 20:41:07 1999
@@ -512,11 +512,6 @@
}
}
- if (result == HTTP_INTERNAL_SERVER_ERROR && r->handler) {
- ap_log_rerror(APLOG_MARK, APLOG_NOERRNO|APLOG_WARNING, r,
- "handler \"%s\" not found for: %s", r->handler, r->filename);
- }
-
/* Pass two --- wildcard matches */
for (handp = wildhandlers; handp->hr.content_type; ++handp) {