I have an old ACF 9 server running as an API to our ERP system. It’s an old unsupported system that needs 32-bit COM support and ver 9 was the last one I could get to work. The system is isolated and only accessed via our internal network. Error emails stopped working a long time ago. Anyways, Starting this morning cfhttp calls to it are not passing cfhttpparams to the ACF 9 server. cfhttp( charset="utf-8", url=http://#util.getSystemSetting(EVEREST")#/item.cfc?wsdl&method=deactivate", result="item", method="POST" ) { cfhttpparam( name="itemCode", type="formfield", value=row.ITEMNO ); } This same line of code was working perfectly last week, now it is not. This is the error we are getting

The ITEMCODE parameter to the deactivate function is required but was not passed in.
 Root Cause: coldfusion.runtime.MissingArgumentException: The ITEMCODE parameter to the deactivate function is required but was not passed in.

Is it safe to assume that you have already checked the data in row.ITEMNO to ensure that it is not passing an empty value or anything like that?

Yes, and I tried a second similar function with a good value and it had the same issue.

so on the "client" side the data is being sent correctly.. have you also done a dump or trace of the form scope on the cf9 server side to see how that parameter is coming across?

The form scope is empty on the cf9 side. I will try with a url var.

wierd... I am not aware of any changes to cfhttp/cfhttpparam that would cause it to not show up in the form scope... could there be something in your onrequeststart or other application.cfm/cfc code that could be clearing out the form scope?

Seems to work fine as a URL value. I'm not sure what the difference would be?

as far as I know it should check both scopes when you hit it via http like that unless your function specifies a particular httpmethod

This new code works fine

ok... it's still wierd that your form scope was empty but at least you got it working.... I'll leave it to the smarter people than me to see if someone can explain why

Thanks for your help, now the trick is to get someone @ adobe to help. @priyank_adobe @Mark Takata (Adobe)

Yeah, this is definitly a duct tape and paper clips type of solution

Are there any potential issues with using URL fields instead of form fields?

assuming this is just a simple value then not likely, unless you have other code expecting that parameter in the form scope

The endpoint is a CFC and the code is using arguments

that is what I assumed.... but you never know what people will do... I've come accross code with form scope refrences within cfc functions

So I think it should be fine. Just wondering about the security of URL vs FORM (as I'm sending it to a CF9 server 😬)

is it over https?

No, I might change that though.

yeah, that is what I am thinking.... if you end up exposing this cf9 api to the public, that is where you will probably want to start taking security more seriously and upgrade your server

This is a old unsupported ERP that needs a 32 COM API. So not able to upgrade the API. We are planning to upgrade the ERP in the next 2 years.

Good lord my phone is blowing up lol, what exactly is the ask here?

you could set up a firewall on your API to whitelist the IPs of the client servers

@Scott Bennett That is currently the setup

This used to work then stopped sending the variable:

cfhttpparam( name="itemCode", type="formfield", value=row.ITEMNO );

changing the type to url got it to pass the value to the cfc

cfhttpparam( name="itemCode", type="url", value=row.ITEMNO );

In CF9? Pretty sure no changes, no.

No, in cf2021

client side (cfhttp) is 2021, receiving side is cf9

Might be a TLS issue?

you are using http

oh, that's right

My first instinct would be to check all your certificates. Also TLS1 got killed in a lot of places, so I'm wondering if the web server is seeing an old protocol and is blowing up. Did you update anything serverwise anywhere?

This request is http not https.... Cavan you can probably dump the cgi scope on the cf9 side to see if it is being switched over to ssl or something. it possible your cf9 server is redirecting the request at the web server level?

This app is running on commandbox docker. I believe it pulls fresh files from adobe on every start. This is a http request.

And did the issue begin occurring right after a cf update?

I don't believe so

maybe a command box issue?

Command box Docker using which image? The official Adobe? Also on aws or Docker hub?

Maybe, I asked in box-products too

None at all that I can think of.

@Scott Bennett @Mark Takata (Adobe) Little update on this. Enabling TLS 1.2 and adding SSL to the CF9 Server in question allows FORMFIELDS to pass with the request. This resolves the issue.