HTTP Compression with Web Forms: How to Identify it is working?

2 posts, 1 answers
  1. Brian Mains
    Brian Mains avatar
    485 posts
    Member since:
    Oct 2008

    Posted 24 Feb 2010 Link to this post


    With IIS compression turned on in IIS 6, the port 80 web site reports that the site has compression turned on.  However, with it turned off and your RadCompression enabled (including ViewState compression), it reports the app as uncompressed.  I think I know why this is happening, but I was wondering if this is a valid way to determine if a site is enabled, and how to figure out that it is working.

  2. Answer
    Daniel avatar
    4949 posts

    Posted 25 Feb 2010 Link to this post

    Hello Brian,

    This website won't help you determine whether the compression is turned on or not. By default RadCompression doesn't compress the response on postback. Even if it is enabled explicitly, the compression will be applied after the first AJAX request / postback, and not initially. Note, that text/html responses from GET requests won't be compressed.

    "So, if RadCompression does not cover all HTTP traffic, what does it cover? Quite simply, RadCompression will automatically detect and compress requests that expect these content response types (as found in the HTTP request's "ContentType" header or "AcceptsTypes" header):

        * application/x-www-form-urlencoded
        * application/json
        * application/xml
        * application/atom+xml"

    You can easily check whether the compression is enabled if you check the response headers (content-encoding) with some tool like Firebug.

    For more information, please examine the following help topic:
    RadCompression help topic

    the Telerik team

    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.
Back to Top