hege wrote:
Chunked is really just a different transfer encoding, nothing to do with multiple gets. You can google for details..
I read section 3.6.1 of RFC 2616 again: it appears that "chunked" simply allows an HTTP response to have multiple segments with their own length fields, making it easier to assemble separate streams into a single Web page/document. This would probably be easy to add to HAVP, but I wouldn't much like forking my own branch of the HAVP source to do so.
hege wrote:
There are some fixes, in order of preference:
1) Use Squid 2.6-STABLE10, it has chunked support. Than HAVP will never see it.
I thought of using Squid, but decided against it, as my SOHO LAN is too small to really need caching, and the fewer services to secure and support, the better.
hege wrote:
2) Let HAVP strip Accept-Encoding header from clients, but that will result in bandwidth wasted (servers don't send gzip compressed data then). I guess it could be made into config option. But using Squid is a must in my opinion anyhow.
Cheers,
Henrik
I already use Privoxy between the browser/clients and HAVP, and Privoxy strips the "Accept-Encoding" headers (since it wants to filter the data, and isn't itself willing to do any gunzipping). Unfortunately, that doesn't seem to dissuade the zdnet.com blog server from using chunking.