Hi all,
Difficult design choice. http://code.google.com/p/cherokee/issues/detail?id=484 The following scenarios exist: index.html.gz theworld.kmz Now Alvaro's opinion is to send these files as: index.html.gz; content-type: text/html content-encoding: gzip theworld.kmz; content-type: application/vnd.google-earth.kml+xml content-encoding: gzip I'm against this because of the following: 1) I *think* that the file is stored on disk as index.html.gz, theworld.kmz but it is not gzipped anymore, actually it would be inflated. 2) The compressed file can have a completely different content type. This counts for kmz but also svgz. For example: application/vnd.google-earth.kmz My suggestion would be informing the mimetype list with the fact that a mimetype or extention is already compressed. And not apply the deflate or gzip algorithm again on this file. The file is served with the specified content type, thus a .gz as gzip, a kmz as vnd.google-earth.kmz. But these types will not be 'recompressed'. Additionally I would suggest not to send the compressed version if the compressed version equals or exceeds the uncompressed filelength + compression header. Stefan _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
