Transfer-Encoding: chuunked AND Content-Encoding: deflate

Transfer-Encoding: chuunked AND Content-Encoding: deflate

Post by dbi » Wed, 28 Jul 1999 04:00:00

using zlib

with HTTP/1.1

I am attempting to send
Transfer-Encoding: chunked
Content-Encoding: deflate

(from a home-built web server)

to a client browser that has indicated its willingness to accept this:
GET / HTTP/1.1
Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/, application/msword, application/, */*
Accept-Language: en,en-ca;q=0.9,de;q=0.8,fr;q=0.7,it;q=0.6,es;q=0.4,da;q=0.3,he;q=0.2,yi;q=0.1
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 5.0; Windows 95; DigExt)
Connection: Keep-Alive

Ive RFC'd myself and tested the component peices individually . successfully.
my interpretation of the RFC leads me to format my HTTP response as:

chunksize n
chunksize n
chunksize 0

where n is the size of the deflated data

I am applying this deflation to arbitrary mime types and
maintaining the original mime-type.

if i had a website to look at that DOES do this successfully
I could compare  the output to see what I am doing wrong.. or indeed if
my browser is not handling it properly.

Does my interpretation of the RFC as to the format of the chunked and compressed
output seem correct?

Thanks in advance..