tracker issue : CF-4181591

Please fix this bug asap . Due to this bug our API's are not working and we cannot be changing URLs in production to fix this .

Vote by External U.

This error is blocking for my project as well. Please have it fixed as soon as possible.

Vote by External U.

https://chl-author-preview.corp.adobe.com/content/help/en/coldfusion/cfml-reference/reserved-words-and-variables/reserved-words.html Let me know if it's good to be made live.

Comment by Saurav G.

Please fix this bug ASAP!

Vote by External U.

The link doesn't work for me https://chl-author-preview.corp.adobe.com/content/help/en/coldfusion/cfml-reference/reserved-words-and-variables/reserved-words.html

Comment by External U.

This is a behavior that we introduced in ColdFusion 11 Update 1, after we fixed the following bug: https://bugbase.adobe.com/index.cfm?event=bug&id=CF-3791392. We will document the above behavior . Thanks, Suchika.

Comment by Suchika S.

This is not an issue for me in CF11. The url works fine for me when running my app in CF11 update 9, but fails in CF2016 Update 2

Comment by External U.

+1 please fix. Note for anyone who finds this bug report: You can remove the mapping by going to cfinstall/cfusion/wwwroot/WEB-INF/web.xml. Search for the api servlet-mapping and comment it out. As the bug tracker does not seem to cross-reference bug reports. This seems to relate to: https://tracker.adobe.com/#/view/CF-4126451 https://tracker.adobe.com/#/view/CF-4198400

Vote by John W.

This is not related to CF11. It is the API manager mapping in /WEB-INF/web.xml which hi-jacks the URL. This should only be applied, if when installing, the API manager is also installed so it doesn't break lots of existing applications.

Comment by John W.

Agree with John. CF should not presuppose the API Manager will be used (this will almost always NOT be the case), and the API Manager should not pre-suppose it can simply steamroll URLs starting with /api. It should just be an install option to pick a value for this. If it had a default, it should be something less likely to already be in use.

Comment by Adam C.

Agree w/ Adam, from start to finish. Also, most? CF users wouldn't even have access to web.xml. Warrants re-think. Thanks!, -Aaron

Comment by Aaron N.

I just voted for this in CF-4198400 too.

Vote by David B.

Saurav above links to the CF docs for the reserved words page. While he offers an internal-only link, and the correct link is instead https://helpx.adobe.com/coldfusion/cfml-reference/reserved-words-and-variables/reserved-words.html, I don't see any reference to /api as being reserved. Then again, that's the CFML Reference, and really talking about reserved words in the language. This is more about a reserved word in URLs (and /rest is another). I hope someday Adobe may address this issue, of /api references failing with already-existing URLs (folders) with that name. As Aaron N says above, not everyone could readily tweak the web.xml (and worse, someone may do it to "fix" their problem and not realize that they now have broken the CF REST feature's reliance on that /api URL.)

Comment by Charlie A.

 /api mapping was used internally in CF for the REST discovery feature of the API Manager. Now we have got the mapping name changed to /cfapiresources . So, creating URL with /api in it or creating a folder named 'api' in CF's webroot should be accessible now. This is fixed in CF2018 and should be available in GM Build. For CF2016 this fix should be available in next bug-fix update.

Comment by Nitin K.

I should note that even after removing the mapping, the default document of index.cfm still does not appear to be working. I can confirm that default document / welcome-file-list is working for other folders.

Comment by Justin T.

For those who come across this in the future, there are a couple of things to note (as of my writing now in Sep 2019). First some good news: as Nitin said here in Apr 2018, they DID change CF2018 so that this problem is gone. The internal references to an /api folder, that were causing conflicts with those wanting to use their own, were indeed changed instead to /cfapiresources (which was ok to have "cf" in the name, because it was a path used only by the CF API Manager, not something exposed publicly). Second, some bad news: Nitin had said here also then that an update for CF2016 would be released to fix this there. That has not happened, even as of CF2016 update 11, the latest at this writing. Finally, to Justin's question (and anyone else on CF2016 still), it's NOT enough to comment out the web.xml file's references to /api, as discussed in comments above. That takes care of one part of the processing (and is indeed all you need if you use the built-in web server in CF). But if you are using IIS or Apache, then there is one more change you need to make (assuming you want to use your own /api folder and do NOT plan to have the CF Enterprise API Manager trying to discover services in your CF instance). There's a file which maps calls from those web servers into CF, named uriworkermap.properties. It too has a /api mapping, in CF2016 at least (no longer so in CF2018, and never in CF11 or 10). That file will be found in any of the *numbered* folders under the coldfusion2016/config/wsconfig folder. such as wsconfig/1/. In that file, find the line with such a /api mapping. Then to comment it out, put a # in front of it. Restart the web server (or in IIS, you could restart just the IIS application pool using this connector, if you understand what I mean). There is no need to restart CF. Now you will find that requests to a url with /api/, whether with or without a file name, will work. And Nitin or other Adobe folks, will this ever be propagated into CF2016, as planned?

Comment by Charlie A.

Correction to my last comment: that may apply to CF11 as well. Let me explain. I see now that I had noted in that other tracker entry on this issue (4198400) that I did find this /api impact happening to CF11, as of its update 11. I wrote that in Apr 2018. I just checked one server I have still running CF11, and I do see that /api entry in the uriworkermap.properties. If you are on 11 and see it, what I wrote above applies (if you want to comment it out). If you are on CF11 update 11 or greater and do NOT see it, perhaps it's only put there if the web connector has been created after that update 11 was put in place. So beware that it may "show up" if someone does the update and updates the connector. Indeed, I should have added to my comment above that even in CF2016 (and CF11, after update 11), you would need to remember to make the change in the uriworkermap.properties file in any NEW web connector that you (or someone administering your server) may create. Same if you "update" a connector in CF11 by removing/re-adding it, or in CF2016 if you use the wsconfig tool's "update" feature and that update were to implement a new uriworkermap.properties file (which has happened with some connector updates over the years). But again, none of this applies to CF2018, as Adobe changed it to NO LONGER use this /api folder, but instead now uses /cfapiresources.

Comment by Charlie A.