tracker issue : CF-3353222

select a category, or use search below
(searches all categories and all time range)
Title:

ColdFusion 10 doesn't gzip responses. This worked fine with the same configuration in ColdFusion 9.

| View in Tracker

Status/Resolution/Reason: Closed/Withdrawn/NotABug

Reporter/Name(from Bugbase): jj j / jj j (John Cambridge)

Created: 10/25/2012

Components: Web Container (Tomcat)

Versions: 10.0

Failure Type: Performance Issue

Found In Build/Fixed In Build: Final /

Priority/Frequency: Major / All users will encounter

Locale/System: English / Win 2008 Server R2 64 bit

Vote Count: 1

Problem Description:
ColdFusion 10 doesn't gzip responses for .cfm files.  This worked fine with the same configuration in ColdFusion 9 when dynamnic compression was turned on in IIS 7.5.  

Steps to Reproduce:
Request a .cfm file in ColdFusion 10 64-bit running on IIS 7.5 64-bit with dynamic compression turned on.  The response will not be compressed.

Also reported on: http://forums.adobe.com/message/4661128

Actual Result:
Not gzipped.

Expected Result:
Should be gzipped.

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3353222

External Customer Info:
External Company:  
External Customer Name: John Cambridge
External Customer Email:  
External Test Config: ColdFusion 10 Standard 64-bit.

Windows Server 2008 R2 64-bit

IIS 7.5 64-bit

Attachments:

Comments:

Compressing files will save us 80% of the bandwidth, improving transfers by that amount. Please escalate this bug.
Vote by External U.
17367 | April 11, 2013 11:49:07 AM GMT
As per our latest findings, served CFM files are compressed correctly when dynamic compression in turned on in IIS 7.5. We were able to verify this on ColdFusion 10, with the latest update, HotFix 13, applied, and also on the ColdFusion Splendor Public Beta. Please do let us know if you are still facing the issue on your side.
Comment by Immanuel N.
17365 | February 20, 2014 08:33:34 AM GMT
Closing the bug as "Not a Bug" since we were not able to reproduce the issue at our end, and did not receive any additional information from the customer. If this bug still exists on your environment, please report back, and we will be reopening this bug.
Comment by Immanuel N.
17366 | December 03, 2014 01:28:49 AM GMT