tracker issue : CF-4198668

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

cfajaxproxy fails to a remote cfc when using Post

| View in Tracker

Status/Resolution/Reason: Closed/Withdrawn/Duplicate

Reporter/Name(from Bugbase): Matthew Hunnell / Matthew Hunnell ()

Created: 05/12/2017

Components: CFComponent

Versions: 2016

Failure Type: Others

Found In Build/Fixed In Build: 2016,0,04,302561 /

Priority/Frequency: Normal / All users will encounter

Locale/System: / Win 2012 Server x64

Vote Count: 0

Problem Description:
We are trying to migrate from cf11 to cf2016. Much of our code is failing because 2016 does not handle remote cfcs the same when accessing them via cfajaxproxy post. It looks like it is on th ajaxproxy side. My guess is that cfajaxproxy is the problem. We can't migrate without this fix or dozens of hours of re-coding to dump cfajaxproxy.

The variables that are passed are not recognized by the remote cfc leadding to "The VARIABLENAMEHERE parameter to the myFunctionName function is required but was not passed in".

Steps to Reproduce:

I built a simple example. Please see the attached files. 

CFM FILE:
<cfajaxproxy cfc="testCFajaxProxy" jsclassname="p" />
<script type="text/javascript">
function runTest() {
	var instance = new p();
	instance.setHTTPMethod("POST");
	var result = instance.testProxy('Test String');
	alert(result);
}
</script>
<input type="button" value="Try it!" onClick="javascript:runTest();" />

CFC FILE:
<cfcomponent>
	<cffunction name="testProxy" access="remote" returntype="string" output="no">
		<cfargument name="var1" type="string" required="true">
   
		<cfset local.returnVar = arguments.var1 & ' testProxy function added some text. '>
		
        <cfreturn local.returnVar>
    </cffunction>	
</cfcomponent>	

Actual Result:

Expected Result:

Any Workarounds:

Attachments:

  1. May 12, 2017 00:00:00: testCFajaxProxy.cfc
  2. May 16, 2017 00:00:00: testcfajax.cfm

Comments:

How does the JavaScript code generated by cfajaxproxy look like?
Comment by Bernhard D.
733 | May 16, 2017 09:24:31 AM GMT
looks like a duplicate of CF-4198589.
Comment by Piyush K.
734 | May 16, 2017 12:38:21 PM GMT
This was marked as a duplicate, but the bug cited in the comment above ( CF-4198589 ) does not come up when I search. Can you please tell me how to follow the progress on this bug.
Comment by Matthew H.
735 | May 16, 2017 01:40:50 PM GMT
On a dev server I installed CF2016 update 2 and did not see this issue. I updated to update 4 and the issue started occurring again with the same code listed.
Comment by Matthew H.
736 | May 16, 2017 02:47:52 PM GMT
Is related to https://tracker.adobe.com/#/view/CF-4198656
Comment by John W.
737 | May 18, 2017 10:48:53 AM GMT