Search

EnableDecompression does not remove AcceptEncoding: gzip header by robertjb

Closed
as Fixed Help for as Fixed

1
0
Sign in
to vote
Type: Bug
ID: 103330
Opened: 7/20/2005 8:31:14 AM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
Trying to use IIS 6 dynamic compression on an application that provides web services to my ASP.Net web site. Setup compression just fine, on the ASP.Net client request set the EnableDecompression="true" so that the client could decompress the content, which works fine. Set the value to "false" so would not use compression while developing so we can debug. The client request still contains the AcceptEncoding: gzip header, so the server still sends it back compressed.
Details (expand)
Product Language
English
Version
Visual Studio 2005 Beta 2
Category
Other
Operating System
Windows Server 2003
Operating System Language
English
Steps to Reproduce
Setup a web reference to a web service, using the proxy class set the EnableDecompression = "false" and do a network trace, see that AcceptEncoding: gzip is included still which tells the server to use compression.
Actual Results
Web server sends back compressed content
Expected Results
Web server send back uncompressed content
Sign in to post a comment.
Posted by Microsoft on 8/24/2005 at 9:10 AM
Hi Robert,

This issue has now been fixed. Please also note that as part of the fixed we changed the default value of EnableDecompression to be false by default. We were concerned that having it on by default would break existing customers that had implemented decompression on top of ASP.NET Web Services in v1.1.

Thank you for helping us identify this issue, and please let me know if you have futher questions or concerns.

Daniel Roth
ASMX
Posted by Microsoft on 8/18/2005 at 6:46 PM
The Microsoft Sub-status is now "Working on solution"
Posted by Microsoft on 8/18/2005 at 11:50 AM
Hi Robert,

Could you please tell me why you were trying to disable automatic decompression? Was this just for test purposes?

Also, are you migrating a .NET 1.1 application to .NET 2.0? If so, did you implement decompression for your 1.1 application?

We are in the process of trying to get this issue fixed, but we need as much customer data as possible in order to justify making a fix and risk destabilizing the product.

Thank you for your help

Daniel Roth
ASMX
Posted by Microsoft on 8/8/2005 at 2:22 PM
Thank you for reporting this issue. I have verified that this issue exists and I am assigning this issue to our developement team. We will notify you once the issue has been resolved.

Thanks again!

Daniel Roth
ASMX
Posted by Microsoft on 7/26/2005 at 5:31 PM
Thank you for submitting this issue. We'll provide an update on status when we have more information.

-The Web Platform & Tools Team
Sign in to post a workaround.