You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apache-bugdb@apache.org by Jeff Lewis <le...@stanford.edu> on 1998/02/14 00:40:01 UTC
Re: mod_mime/1799: mod_mime's mapping to handler and content_type
gets confused by some filenames
The following reply was made to PR mod_mime/1799; it has been noted by GNATS.
From: Jeff Lewis <le...@stanford.edu>
To: Dean Gaudet <dg...@arctic.org>
Cc: apbugs@apache.org
Subject: Re: mod_mime/1799: mod_mime's mapping to handler and content_type
gets confused by some filenames
Date: Fri, 13 Feb 1998 15:39:35 -0800
> Your change probably breaks some legitimate uses of SetHandler and such.
It seems like the change would only affect AddHandler mappings,
since SetHandler is applied after and overrides the extension mappings.
But if you don't like that, how about adding a "default" or "none" keyword
to SetHandler and AddHandler so it's possible to clear the handler that
gets assigned to a file? Right now, if I want to have a directory full
of GIFs, and have them all served regardless of extensions, including any
extensions that get added in the future, I can't do it because there's
no way to say "SetHandler to nothing so you do that default server thing
where you just copy this file out". If I put
ForceType image/gif
in that dir, any file with, for instance, ".asis.gif" or ".map.gif"
or ".map" will get a handler assigned and it'll choke. But if I could
also do
SetHandler default
or
SetHandler none
everything would work fine regardless of extensions. And if I want to
worry about it on a server-wide basis, I can put
AddHandler default gif
in my server conf. It just seems that the common, uncomplicated,
and reasonable user expectation is that, if my file ends in ".gif"
it's an image and I want it served.
thanks,
Jeff