Use of program names for the identification of encoding formats is not desirable and is discouraged for future encodings. Their use here is representative of historical practice, not good design. For compatibility with previous implementations of HTTP, applications SHOULD consider "x-gzip" and "x-compress" to be equivalent to "gzip" and "compress" respectively.
- An encoding format produced by the file compression program "gzip" (GNU zip) as described in RFC 1952 . This format is a Lempel-Ziv coding (LZ77) with a 32 bit CRC.
- The encoding format produced by the common UNIX file compression program "compress". This format is an adaptive Lempel-Ziv-Welch coding (LZW).
For compatibility with previous implementations of HTTP, applications SHOULD consider 'x-gzip' and 'x-compress' to be equivalent to 'gzip' and 'compress' respectively.maybe should be replaced by word 'future'.
Do you think so?