21,886
社区成员
发帖
与我相关
我的任务
分享HTTP 1.0是否支持数据压缩
HTTP 1.0是否支持数据压缩？刚才看了一下rfc文档(2616)，http1.1本身的就是一种启动数据压缩的，那么我看到的代码中怎么去做编码格式判断是否支持数据压缩那？奇怪。我认为如果HTTP1.0不支持数据压缩传输，那么就判断它，把用赶出去。其他的就直接调用压缩代码压缩数据咯 呵呵！:)
...全文
请发表友善的回复…
发表回复
icb 2002-03-02
- 打赏
- 举报
很简单的问题 就是HTTP1.0是否支持压缩编码后传输数据！就这个问题！
RobinCat 2002-03-02
- 打赏
- 举报
失败～看不懂～～
我很打自己的脸…
我很打自己的脸…
icb 2002-03-01
- 打赏
- 举报
你等于什么也没说！
yorgo 2002-02-28
- 打赏
- 举报
要你的浏览器支持
icb 2002-02-17
- 打赏
- 举报
gzip An encoding format produced by the file compression program
"gzip" (GNU zip) as described in RFC 1952 [25]. This format is a
Lempel-Ziv coding (LZ77) with a 32 bit CRC.
compress
The encoding format produced by the common UNIX file compression
program "compress". This format is an adaptive Lempel-Ziv-Welch
coding (LZW).
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.
deflate
The "zlib" format defined in RFC 1950 [31] in combination with
the "deflate" compression mechanism described in RFC 1951 [29].
"gzip" (GNU zip) as described in RFC 1952 [25]. This format is a
Lempel-Ziv coding (LZ77) with a 32 bit CRC.
compress
The encoding format produced by the common UNIX file compression
program "compress". This format is an adaptive Lempel-Ziv-Welch
coding (LZW).
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.
deflate
The "zlib" format defined in RFC 1950 [31] in combination with
the "deflate" compression mechanism described in RFC 1951 [29].
