W3C home > Mailing lists > Public > www-svg@w3.org > March 2014

Re: mime-type and mime-encoding for .svgz

From: Bjoern Hoehrmann <derhoermi@gmx.net>
Date: Mon, 31 Mar 2014 15:09:33 +0200
To: Bob Tennent <rdt@cs.queensu.ca>
Cc: www-svg@w3.org
Message-ID: <2vpij9da3655r4dkthsa76ddvacvkc51ht@hive.bjoern.hoehrmann.de>
* Bob Tennent wrote:
> >|>My interpretation of the w3c recommendations is that a .svgz
> >|>file should be served with Content-Type: image/svg+xml and
> >|>Content-Encoding: gzip. Am I wrong?
> >|
> >|You are correct, a gzipped SVG file should be served with those two
> >|headers. http://marc.info/?l=thttpd&m=139491235425779&w=2 seems to be
> >|the most mistaken message in the thread, if someone wants to respond.
>Thanks.  But the most important message to respond to is
>because he's the author of the thttpd software. If he doesn't think
>the .svgz extension indicates *both* an encoding *and* a mime-type,
>there's no way the software will be fixed.

If he does not want to support a configuration that lets users set the
Content-Encoding and Content-Type header based on a file extension then
that is his choice to make; there is nothing particularily wrong with
that. A workaround for users would be to uncompress the file and let the
server handle compression and headers, assuming thttpd supports that.
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 
Received on Monday, 31 March 2014 13:10:02 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:54:52 UTC