RE: contentEncoding header with empty body

Er, I mean that the outfault message not the output message.  And it's not
supposed to be gzipped...  The test suite is incorrectly looking for gzip
here.  I'll include that fix in my check-in.


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 Jonathan Marsh
> Sent: Monday, February 19, 2007 10:43 AM
> To: keith@wso2.com
> Cc: www-ws-desc@w3.org
> Subject: RE: contentEncoding header with empty body
> 
> 
> I think this is GIGO with the test framework.  The simplest fix is to add
> whttp:contentEncoding="" to the <input> binding operation, so we don't
> have
> to look for these edge cases when generating the assertions.  The test
> case
> will still test what we want it to, which is that the <output> message is
> gzipped.
> 
> I'll check in such a fix shortly.
> 
> Jonathan Marsh - http://www.wso2.com -
> http://auburnmarshes.spaces.live.com
> 
> 
> > -----Original Message-----
> > From: Keith Chapman [mailto:keith@wso2.com]
> > Sent: Saturday, February 17, 2007 9:11 PM
> > To: Jonathan Marsh
> > Subject: contentEncoding header with empty body
> >
> > Just missed another thing regarding MessageTest-3G.
> > |CodedEchoHTTPBinding |Binding has contentEncodingDefault as gzip. This
> > in effect makes the contentEncoding of the operation GuaranteedFault
> > gzip. The issue is that there is no input to GuaranteedFault and hence
> > its body is empty. There is nothing bto be gziped. Is the gzip header
> > needed in this case too? The framework looks for it.
> >
> >
> > Thanks,
> > Keith.

Received on Monday, 19 February 2007 19:16:33 UTC