EnableDecompression on a 2.0 web client
Davy J <[email protected]> Fri, 2 Feb 2007 11:10:34 +0100
| Newsgroups | gmane.comp.windows.devel.dotnet.cx |
|---|---|
| Message-ID | <[email protected]> |
Hi,
I've looked all over the web for this one and it seems as I'm the
only one with the problem
After creating the webservice proxy in VS2005 , modify the code to
enable decompression
Service svc = new CentralData.Service();
svc.EnableDecompression = true;
I'm repeatedly getting a "InvalidOperationException" with the contents
of the zipped stream as the source, has anyone else had this problem
or knows a work around. It seams that 2.0 isn't receiving the correct
headers , or has a problem identifying or dezipping the stream?
From RFC I found
14.11 Content-Encoding
The Content-Encoding entity-header field is used as a modifier to the
media-type. When present, its value indicates what additional content
codings have been applied to the entity-body, and thus what decoding
mechanisms must be applied in order to obtain the media-type
referenced by the Content-Type header field. Content-Encoding is
primarily used to allow a document to be compressed without losing
the identity of its underlying media type.
Content-Encoding = "Content-Encoding" ":" 1#content-coding
Content codings are defined in section 3.5. An example of its use is
Content-Encoding: gzip
I've checked the stream with proxyTrace ( pocketsoap.com) and the
Content-Encoding header is correct with the correct capitalization.
Thanks
Dave
--
Dave Jones
===================================
This list is hosted by DevelopMentor® http://www.develop.com
View archives and manage your subscription(s) at http://discuss.develop.com