Hi Nick,
Thanks for the response. Pipelining of deflate and chunking filters is
exactly what I am seeing Apache perform -- just didn't know what to call
it. To rephrase the question, does the HTTP 1.1 RFC address how to
handle the layering of a chunked transfer encoding on top of a gzip
content
On Sat, 13 Sep 2008 15:53:10 +0100
Nick Kew <[EMAIL PROTECTED]> wrote:
> On Sat, 13 Sep 2008 11:02:11 -0300
> Michael Caplan <[EMAIL PROTECTED]> wrote:
>
> > 1. the gzip content encoding happens on the entire body before it
> > is chunked.
> > 2. the ungzipping happens on the entire body after
On Sat, 13 Sep 2008 11:02:11 -0300
Michael Caplan <[EMAIL PROTECTED]> wrote:
> 1. the gzip content encoding happens on the entire body before it is
> chunked.
> 2. the ungzipping happens on the entire body after it is dechunked.
Exactly.
> If I got this right (which I don't think I do), the w
Hi,
I have a question about how Transfer-Encoding: chunked works with a
Content-Encoding gzip. Reading the HTTP 1.1 RFC,
http://en.wikipedia.org/wiki/Chunked_transfer_encoding and other
discussions on the net that touch on this subject I'm a little confused
on how the web server and browser
Jim Britain wrote:
Re: http://en.wikipedia.org/wiki/HTTP_ETag
http://www.iwaw.net/04/Clausen.pdf -- (paragraph: 10)towards the
end... (worth reading the whole thing) -- details are a little buried,
pointing toward further research in Apache docs/code.
Very nice refs, thanks.
Information pr
Jim Britain wrote:
On Sat, 13 Sep 2008 08:13:51 +0100, "dave selby"
<[EMAIL PROTECTED]> wrote:
2008/9/12 Scott Gifford <[EMAIL PROTECTED]>:
"dave selby" <[EMAIL PROTECTED]> writes:
Is there a way for me to turn off if-modified-since so the client
browser will ALWAYS use its locally cached do
On Sat, 13 Sep 2008 08:13:51 +0100, "dave selby"
<[EMAIL PROTECTED]> wrote:
>2008/9/12 Scott Gifford <[EMAIL PROTECTED]>:
>> "dave selby" <[EMAIL PROTECTED]> writes:
>>
>>> Is there a way for me to turn off if-modified-since so the client
>>> browser will ALWAYS use its locally cached document
>>
2008/9/12 Scott Gifford <[EMAIL PROTECTED]>:
> "dave selby" <[EMAIL PROTECTED]> writes:
>
>> Is there a way for me to turn off if-modified-since so the client
>> browser will ALWAYS use its locally cached document
>
> Dave,
>
> Usually sending an Expires header will tell browsers to mostly use a
>