tracker issue : CF-3352466

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

Upgrading to 9.0.1 causes clients with cached cfajax.js to generate WDDX packet parse errors

| View in Tracker

Status/Resolution/Reason: Closed/Won't Fix/LowImpact

Reporter/Name(from Bugbase): Steve Hammonds / Steve Hammonds (Steve Hammonds)

Created: 10/24/2012

Components: AJAX

Versions: 9.0.1

Failure Type: Non Functioning

Found In Build/Fixed In Build: 9.0.1 /

Priority/Frequency: Critical / Most users will encounter

Locale/System: English / Win 2008 Server

Vote Count: 0

Problem Description:
Upgrading to 9.0.1 (and apparently CF10) updates the cfajax.js file.  Clients that have cached the old version of cfajax.js make improper calls to the updated method (arguments have changed).  This causes the error "WDDX packet parse error at line 1 column 1. Content is not allowed in prolog".  Sending no cache headers is not enough to prevent all browsers from caching these files.

This could easily be fixed if:
1. CF used a different file name for cfajax.js when it gets updated (cfajax0901,js, cfajax10.js, etc.)
2. or CF appended a timestamp url to the include for the cfajax.js that is generated to prevent caching.

Steps to Reproduce:
Hard.  Create a web page with a cfajaxproxy tag and a call to a cfc method.  Have a client visit the page.  Upgrade to 9.0.1 and have the client visit the page again.

Actual Result:
WDDX packet parse error at line 1 column 1. Content is not allowed in prolog

Expected Result:
Working cfajaxproxy call

Any Workarounds:
Setting no cache headers in web server for /CFIDE/scripts/ajax/package folder.  Does not work for stubborn browsers.

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

Watson Bug ID:	3352466

External Customer Info:
External Company:  
External Customer Name: hammo7
External Customer Email:  
External Test Config: Windows Server 2008, 32 bit

IIS 7.5

CF 9,0,1,274733  Standard

Attachments:

Comments:

Documented in this thread: http://www.raymondcamden.com/index.cfm/2009/10/18/Ask-a-Jedi-ColdFusion-Ajax-example-of-retrieving-fields-of-data-2#cCD412C3C-A164-E817-33B46EEFD6BEBD79
Comment by External U.
17383 | October 24, 2012 03:48:17 PM GMT
Same problem. We upgraded from CF8 to CF10, and all IE9 users had this issue. For our administrators, it's not an issue to ask them to clear their browser cache (which fixes the issue). Unfortunately front-end clients are receiving the same error constantly. We tried adding no-cache headers to the /CFIDE/scripts/ajax/ (and all sub-folders). We also added no-cache headers to all pages that use cfajaxproxy. Neither worked for IE clients. A quick Google shows that there are tons of people having this problem.
Comment by External U.
17384 | December 17, 2012 07:45:25 PM GMT
Related bug CF-3350039 (Comment added from ex-user id:vnigam)
Comment by Adobe D.
17385 | December 17, 2013 01:54:21 AM GMT