diff --git a/master/conform.html b/master/conform.html index fd3d21f5..d7c3d387 100644 --- a/master/conform.html +++ b/master/conform.html @@ -845,17 +845,42 @@
-Compression of stored content (the "entity," in HTTP -terms) is distinct from automatic compression of the message body, as +
+In HTTP, compression of stored content (the "entity") is distinct from automatic compression of the message body, as defined in HTTP/1.1 TE/ Transfer Encoding -([rfc2616], sections 14.39 and 14.41).
+([rfc2616], sections 14.39 and 14.41). +If this is poorly configured, +and the compression specified in the HTTP headers does not match the used values, +SVG user agents are required to treat the document as being in error. + ++Configuring a server to handle both SVG and SVGZ files +means that it must be able to assign the same media type to both types of files, +but with different compression headers. +Some commonly used servers do not support this configuration in an easy or efficent way, +because compression behavior is configured based on media type. +
++With most modern web servers, it is often easier to upload uncompressed SVG files instead of SVGZ files. +Then, rely on the server to compress the file for transmission, +and cache it for future request, +using the same server instructions as for other text-based file formats such as HTML. +This also allows the server to use newer compression methods, +when they are supported by the user agent requesting the file. +
++Alternatively, the web server may be able to correctly process pre-compressed SVGZ files +if they are first renamed to use the .svg.gz compound file extension. +The server would still need to be configured to support static gzip-compressed files. +
+