tracker issue : CF-3750729

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

<cfclient> seems to require /CFIDE to be available

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/NeedMoreInfo

Reporter/Name(from Bugbase): Adam Cameron / Adam Cameron (Adam Cameron)

Created: 04/27/2014

Components: Mobile Support, Language Syntax

Versions: 11.0

Failure Type:

Found In Build/Fixed In Build: PublicBeta / 2016

Priority/Frequency: Major / Some users will encounter

Locale/System: English / Platforms All

Vote Count: 2

Long version:
http://cfmlblog.adamcameron.me/2014/04/coldfusion-11-cfclient-seems-to-require.html

TL;DR:
<cfclient> requires /CFIDE to be exposed.

Obviously it shouldn't.

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

Watson Bug ID:	3750729

External Customer Info:
External Company:  
External Customer Name: Adam Cameron.
External Customer Email:  
External Test Config: My Hardware and Environment details:

Attachments:

Comments:

This needs to be fixed before final release.
Vote by External U.
12547 | April 28, 2014 08:49:10 AM GMT
+1 this needs to be fixed in CF11 Update 3
Vote by External U.
12548 | November 15, 2014 05:36:11 PM GMT
I just started testing the <cfclient> tickets in CF11 Update 3 and ran into this right away. This should've been fixed before CF11's release.
Comment by External U.
12529 | November 15, 2014 05:37:35 PM GMT
What's the "more info" you need here, Adobe?
Comment by External U.
12530 | November 15, 2014 05:43:01 PM GMT
@Adam, yeah, lol Adobe, just remove the /CFIDE mapping (per lockdown guide) and try running <cfclient>hmm</cfclient>
Comment by External U.
12531 | November 15, 2014 06:11:48 PM GMT
"lol Adobe" should've been "lol. Adobe"
Comment by External U.
12532 | November 15, 2014 06:13:03 PM GMT
@Adam/Aaron, the Status here is "ToTest --> Need More Info", and so it is obviously not meant for you. If we need some information from you (i.e community), the status would be "ToTrack --> PRNeedInfo".
Comment by Rupesh K.
12533 | November 24, 2014 09:33:32 AM GMT
I'm not entirely sure why this is an issue anyway. Unless I'm very much mistaken, Cfclient is only used during development of a mobile application, not to power a production site. It is only processed during application testing and packaging, right? If you develop locally, do you lock down your local development environment?
Comment by External U.
12534 | November 24, 2014 04:07:56 PM GMT
No, Rupesh, this is a public bugbase, so if you set the status as "need info" and I'm the person who raised the ticket, the *natural* inference is that you need the info from me. If it was *obvious* you weren't addressing me, then I'd've not have asked you about it, would I? No. If you lot need to exchange info internally, all good, but you should perhaps add a comment "hey [person], need something doing here". As well as there being no ambiguity there, it also indicates you lot are on the case. Cheers, and I appreciate you looking at the issue. That said, Carl, you are mostly right: <cfclient> is a dev tag, and would never seem the light of day in production. I guess I made the mistake of checking <cfclient> on a server which was locked down, so it didn't work. Our dev environments reflect our live environments (not unusual, I should think?), so we don't have /CFIDE available. I also think if one was to list all the things wrong with the premise of "<cfclient>", it needing /CFIDE open is the least of anyone's worries. -- Adam
Comment by External U.
12535 | November 24, 2014 06:28:07 PM GMT
@Adam, cool. I can see locking down Dev to match Production. Maybe I'm too lazy to bother. ;-)
Comment by External U.
12536 | November 24, 2014 07:17:26 PM GMT
@Rupesh, Regarding "the Status here is "ToTest --> Need More Info", and so it is obviously not meant for you. If we need some information from you (i.e community), the status would be "ToTrack --> PRNeedInfo"." Where are these status combinations documented at? I did not see this documented, so it wasn't obvious to me. Thanks!, -Aaron
Comment by External U.
12537 | November 29, 2014 07:18:19 AM GMT
the requirement of /CFIDE to be available for cfclient is only during the packaging or the while accessing the shell application before packaging. This should not be done on a production server. Closing it as not a bug.
Comment by Rupesh K.
12538 | January 05, 2015 08:29:59 AM GMT
Rupesh, While I agree cfclient should never be used on a development server, you can't assume that development servers won't be locked down for security reasons. Even a local development server may be locked down (see Adam's comment below for example) to closely mimic the behavior of a production server. Either you need to not rely on CFIDE being unavailable, or you need to *clearly* document the requirements. Seems like yet another argument for breaking up CFIDE into a small publi-facing set of folders for resources supporting UI tags, and the rest in a by-default locked down folder.
Comment by External U.
12539 | January 05, 2015 06:25:23 PM GMT
As of now, CFIDE is required to be available on the development server. We will get this documented. As far as breaking up CFIDE is concerned, that is already done for CF 12.
Comment by Rupesh K.
12540 | January 06, 2015 12:18:41 AM GMT
Hi Rupesh, https://wikidocs.adobe.com/wiki/display/coldfusionen/Building+Mobile+Applications says: "Type 2 - ColdFusion-deployed web app that can be rendered through the mobile device's web browser." This type requires /CFIDE in production, right? So this ticket should be re-opened? So is the following still true? "the requirement of /CFIDE to be available for cfclient is only during the packaging or the while accessing the shell application before packaging." Thanks!, -Aaron
Comment by External U.
12541 | January 06, 2015 05:42:28 PM GMT
Good point Aaron. I had overlooked that - my bad. Since we have already done the CFIDE separation for CF 12 and thus fixed this issue in CF 12, we need to see if this bugs needs to be fixed separately for CF 11. We can take a call based on how many applications are are being built with the "Type 2" model. Please let us know and we will consider it then. BTW, if you are building mobile applications, please feel free to submit the same for the mobile application contest that we are running.
Comment by Rupesh K.
12542 | January 07, 2015 09:11:59 AM GMT
I think there is a shortfall of the bugbase here Rupesh. This issue is flagged as "need info", and it shows up in a special section in my home page, but it's not ME you need the info from, it's Aaron.
Comment by External U.
12543 | January 19, 2015 03:50:18 AM GMT
Hi Rupesh, Thanks for the information about the cfmobile contest. I do plan to do a cfmobile deep-dive - maybe in the next 2-3 months. My opinion on the 'how many applications are being built with the "Type 2" model' question is that it should be rephrased as 'how many applications are being built, or will be built, with the "Type 2" model during the timeframe that CF11 is supported'. Reason I say that is: CF11 is a supported version and one of its flagship features has a very broken feature here (if Adobe is recommending the Lockdown Guide). I don't think it would be correct to make customers that paid for CF11 wait till CF12 for the fix. Just my opinion tho. Perhaps this ticket here isn't the best place to take a poll. That question probably should be asked more publicly than here. Thanks!, -Aaron
Comment by External U.
12544 | January 19, 2015 06:38:19 AM GMT
Interesting.. why is C:\ColdFusion11\cfusion\wwwroot\CFIDE\cfclient (which is full of .js files) not actually located here C:\ColdFusion11\cfusion\wwwroot\CFIDE\scripts\cfclient? That would've solved this issue from the beginning. Looks like the fix is simple? (just move the cfclient dir into the scripts dir). Thanks!, -Aaron
Comment by External U.
12545 | January 19, 2015 06:43:12 AM GMT
Hi Adobe, I see the Status/Resolution/ReasonCode is "Closed/Fixed/NeedMoreInfo". Which CF11 Update was this fixed in? I understand this issue does not apply to CF2016 (and I've confirmed the same), b/c CF2016 moved the scripts directory out of /CFIDE. But this ticket was filed against CF11, before CF11 was even released. Thanks!, -Aaron
Comment by Aaron N.
12546 | August 04, 2017 04:59:27 AM GMT