Re: The HTTP header to be used for a gzip message

Hi,

We do support Transfer-Encoding:chunked.  When a message is gziped it has to
be a chunked message. Which means if  we use the Transfer-Encoding header
to  indicate gzip, the same header has got to indicate chunked too.  I tried
this combination  with tomcat at the server. The server understands the
message only if the headers are placed as following

Transfer-Encoding: chunked
Transfer-Encoding: gzip

If we reverse the order it returns a 501. The same occurs if we use
"Transfer-Encoding: chunked,gzip " or "Transfer-Encoding: gzip,chunked ".

Taking this into account I'm still not sure which header we should be
using...

What do u think Philippe

Thanks,
Keith.

On 1/13/07, Jonathan Marsh <jonathan@wso2.com> wrote:
>
> FTR, the testcase originally had Transfer-Encoding:chunked which I changed
> because Axis2 didn't support it.  But perhaps changing it to gzip was a
> mistake.  We need to look at this a little deeper.
>
> Jonathan Marsh - http://www.wso2.com -
> http://auburnmarshes.spaces.live.com
>
> > -----Original Message-----
> > From: www-ws-desc-request@w3.org [mailto:www-ws-desc-request@w3.org] On
> > Behalf Of Philippe Le Hegaret
> > Sent: Friday, January 12, 2007 7:49 AM
> > To: keith chapman
> > Cc: www-ws-desc
> > Subject: Re: The HTTP header to be used for a gzip message
> >
> >
> > On Fri, 2007-01-12 at 14:30 +0530, keith chapman wrote:
> > > Hi,
> > >
> > > Does the spec state the HTTP header to use when a message is encoded
> > > as gzip. I  had a look at section "6.3.2 HTTP Transfer Coding
> > > Selection" it does not state anything to this regard. The test
> > > framework looks for the header "Transfer-Encoding=gzip" but axis2 uses
> > > the header "Content-Encoding: gzip" .
> >
> > Given
> > [[
> >   This [Transfer-Encoding] differs from the content-coding in that the
> > transfer-coding is a property of the message, not of the entity.
> > ]]
> > http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.41
> >
> > I believe Transfer-Encoding is the one to use. With the set of value
> > available in section 3.6 of the HTTP RFC [1]. Note that "identity" can't
> > be used anymore in as a transfer codings, according to the latest
> > editors version of the HTTP RFC that includes errata [2].
> >
> > Given your question, the spec needs clarification.
> >
> > Philippe
> >
> >
> > [1] http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.6
> > [2]
> > http://www.w3.org/Protocols/HTTP/1.1/rfc2616bis/draft-lafon-rfc2616bis-
> > latest.html#transfer.codings
>
>
>