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 2004/09/30 15:23:31 UTC
DO NOT REPLY [Bug 31483] -
add svgz in mime.types file
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=31483>.
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=31483
add svgz in mime.types file
slive@apache.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
------- Additional Comments From slive@apache.org 2004-09-30 13:23 -------
It seems quite ambiguous to me if this is really the right thing to do. Is a
gzipped svg file still a plain image/xvg+xml or is it an image/xvg+xml with a
content-encoding implied? I'd tend to believe the latter, in which case it does
not make sense to change the mime.types file unless there is also a
corresponding AddEncoding directive.
The svg spec does not seem perfectly clear on this topic. But I don't see
anywhere where it says that applications conforming to the spec must understand
gzipped documents. So that implies that the gzip is not part of the content
type, and we shouldn't change mime.types.
Feel free to provide evidence to the contrary (and reopen the bug if you do so).
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org