the way to support content-encoding of HTTP1.1

From: 树新 郑 <shuxin.zheng@dont-contact.us>
Date: Fri, 13 Oct 2006 14:56:45 +0800 (CST)

hi, I've seen the patch modules of squid which support http-gzip transfer mode with http1.1. (These modules's url such as: http://devel.squid-cache.org/projects.html#gzip http://devel.squid-cache.org/stale_projects.html#te http://devel.squid-cache.org/stale_projects.html#te_modules) I don't think it is a good idea ton encode and decode the HTTP-GZIP format data in squid, because the squid just only a web-cache proxy, not a web-server like MS-IIS or Apache. And the encoding/decoding process is so spensive, which will be very slowly down the squid. I think it is a goold idea to combine the web-server and client-browser with squid: let web-server and client-browser handle the encoding/decoding work, squid just caching the data of the .html, .jpg,etc., and squid don't need to care about the content of the data is encoded or not, just cache it and transfer it. Inorder to do this, the below way must be completed: 1) add module to make squid can receive data been encoding by support "Transfer-Encoding: chunked" protocol of HTTP1.1. This module is for finding the end of data from web-server; 2) make encoding-status a item of the hash key of the StoreEntry in memory and disk; 3) support PURGE method and refresh mode. Thanks zsx 2006.10.13 ___________________________________________________________ 雅虎免费邮箱-3.5G容量,20M附件 http://cn.mail.yahoo.com/
Received on Sat Oct 14 2006 - 10:26:11 MDT

This archive was generated by hypermail pre-2.1.9 : Wed Nov 01 2006 - 12:00:06 MST