<cfmodule> in CFScript: does this behaviour make any sense?
<cfmodule> is handled in CFScript. Railo and ColdFusion implement it differently (although Railo also implements ColdFusion's implementation for sideways compatibility).
<cfexit> bug I thought I had spotted: solved
<cfexit> wrong, or am I misunderstanding?".<cfexit> is right. However there's still a bug in ColdFusion...<!--- testusingCfimport.cfm --->
<cfimport taglib="." prefix="t">
<t:basic>
Text within tags<br>
</t:basic>
<hr>
<t:basic exitMethod="exittag">
Text within tags<br>
</t:basic>
<hr>
<t:basic exitMethod="exittemplate">
Text within tags<br>
</t:basic>
<hr>
<!--- basic.cfm --->
<cfparam name="attributes.exitMethod" default="">
executionMode: <cfoutput>#thisTag.executionMode#</cfoutput><br>
<cfif thisTag.executionMode EQ "start">
<cfif len(attributes.exitMethod)>
exitMethod: <cfoutput>#attributes.exitMethod#</cfoutput><br>
<cfexit method="#attributes.exitMethod#">
<cfelse>
exitMethod: not specified<br>
<cfexit>
</cfif>
</cfif>
each() function in each of Railo and ColdFusion
#coldfusion sandbox security requires FileRead() because some code uses "new Query()" due to base.cfc. That's a pretty bad design, no?
— Henry Ho (@henrylearn2rock) July 14, 2014
writeLog(), throw() and writeDump() aren't actually functions. Or aren't implemented properly if they are.
#coldfusion stopped supporting UI tags.
RT @udayogra: As decided we won't invest any time in Ajax UI components https://t.co/kWD7vIbddO
— Henry Ho (@henrylearn2rock) June 30, 2014
evaluate() is bad not least of all because it's slow ('"evalulate() is really slow". Is it now?'): that trope ends up being mostly bullshit. So one can't just settle in and accept what once might have been true will thereafter always be true.
restSetResponse() revisited
restSetResponse() has been implemented: "restSetResponse() requires the method to be returntype void. What?". At the time I was looking at how it was instrumental in how "ColdFusion takes something that should be easy and makes it hard" in the context of exception handling. That's slightly edge-case-y, I'll admit it.restSetResponse() is not fit for purpose. Literally: it's not fit for the purpose it has been implemented for.However I am wondering what should be the HTTP status code is the request sent by the client is valid (DELETE mySite/entity/123) and the entity to delete does not exist.Because I was facing the same question (and with GET operations too). The answer is the very obvious:
In that case, the service should return an HTTP 404. Strictly speaking, a DELETE or a GET request for a resource that does not exist is not a "valid" request - ie. the client should not re-attempt that request because it will never succeed... The HTTP protocol defines 2 categories of problems - those with a 4xx status code, where the client must modify the request before retrying it, and those with a 5xx status code, which indicate that the service ran into trouble and the client should/could retry the same exact request without changing it.As I'm perpetually wont to say to people who marvel that REST is some kind of wonderous thing... it's not. It's just "making HTTP requests". We do this every day in our browser. REST requests are no different. So if a resource doesn't exist... 404 the request.
This project aims to make at least some functions from newer versions of Adobe
ColdFusion avilable in older versions. For example, SessionInvalidate() is new
to CF10 but undocumented features make it possible in at least CF8+, possibly
even CF7.
Each set of functions is wrapped within an "if" statement to make sure they
aren't loaded if the version already supports them.
queryExecute(), and there's a bunch of other stuff there too. This is definitely something the CFML community will benefit from, so would be good to get some more community participation going.
/CFIDE/scripts, and /CFIDE really mustn't be exposed to the outside world./CFIDE/scripts to somewhere else "Isolate the /CFIDE/scripts directory from the rest of /CFIDE" (3732913), which says this:
myArray.each()... extending the array whilst iterating..?
.each() method.numbers = ["one","two","three","four"];
numbers.each(function(value,index){
if (value=="one") {
numbers.append("five");
}
writeOutput("Index: #index#; value: #value#<br>");
});
writeDump(var=numbers);
This is just a quick survey to gauge how effective Adobe have been at communicating to their clients regarding security issues that have arisen in ColdFusionThere's seven questions: all bar one can be answered via a mouseclick, and the last asks for a comment. There's other boxes for comments along the way too.