Re: http/1.1 decompress
- From: Joerg Jooss <news-reply@xxxxxxxxxxxxx>
- Date: Sat, 26 Aug 2006 12:18:57 +0000 (UTC)
Thus wrote Frederik,
Kevin,
I don't seem to be able to solve the decompress problem but I have
another
possible solution for my problem.
Maybe you can help me with that.
I should be able to remove the content-encoding field from the header
before
the request is send to the server => the server won't compress the
message
and I can read the response.
So I think I should create a sort of proxy that checks outgoing
messages for
the content-encoding field.
I should capture the messages before they're are being send to port
80, adjust them and do a resend.
The only problem is that I'm not sure how I can create such a
construction.
Do you have an idea how I can start?
To avoid receiving compressed content, make sure *not* to send an Accept-Encoding header with a value of "gzip" or "deflate". .NET 1.x has no built-in support for compression, so just make sure you don't set the header in your code explicitly. In .NET 2.0, set HttpWebRequest.AutomaticDecompression to DecompressionMethods.None.
Cheers,
--
Joerg Jooss
news-reply@xxxxxxxxxxxxx
.
- References:
- Re: http/1.1 decompress
- From: Frederik Vanderhaegen
- Re: http/1.1 decompress
- Prev by Date: datagrid paging automatically (after 10 seconds)
- Next by Date: Accessing a DataRow by name
- Previous by thread: Re: http/1.1 decompress
- Next by thread: Re: http/1.1 decompress
- Index(es):
Relevant Pages
|