You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2006/01/20 13:39:46 UTC
DO NOT REPLY [Bug 38330] New: - Cannot RemoveType which comes from mime.types
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=38330>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=38330
Summary: Cannot RemoveType which comes from mime.types
Product: Apache httpd-2
Version: 2.0.52
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: mod_mime
AssignedTo: bugs@httpd.apache.org
ReportedBy: adrian.vogel@desy.de
It seems you cannot unassign a MIME type from a filename extension (with
RemoveType) which has been declared in the "mime.types" file. Removing types
which have been declared using AddType before works fine.
We wanted to turn ".gz" into an encoding instead of a type, but we weren't able
to do so before commenting out the declaration of "application/x-gzip" inside
"mime.types" (even though modifying that file is discouraged in the manual).
Might it be worthwhile to mention that our "mime.types" file is not located
inside the ServerRoot, but that TypesConfig accepts the absolute path
"/etc/mime.types"?
Is this behaviour intended? The manual does not go into detail on that, but I
think one should be able to remove default type associations from "mime.types"
as well.
Cheers, Adrian
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org
DO NOT REPLY [Bug 38330] - Cannot RemoveType which comes from mime.types
Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=38330>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=38330
------- Additional Comments From bug.apache.amc+0+@nicemice.net 2006-11-29 12:52 -------
I also want .gz to be an encoding, not a type, and .gz does *not* appear in my
mime.types, and still I was unable to use RemoveType .gz to counteract the
AddType in apache2.conf. I had to comment out the AddType. I'm using Debian
package apache2.2-common 2.2.3-3.1 with apache2-mpm-worker 2.2.3-3.1.
What's even stranger is that the filename extension should have been irrelevant,
because I was using a type map:
URI: home
URI: home.html
Content-Type: text/html; qs=1
URI: home.html.gz
Content-Type: text/html; qs=1
Content-Encoding: gzip
A request for home.var would yield a content-type of application/x-gzip, which
isn't even mentioned in the type map. Similarly, if I changed the content-tpe
in the .var file to foo/bar, I would still get text/html. Surely the explicit
instructions in home.var should override any filename-based type/encoding
determination.
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org