did the trick! AWESOME! thanks @aliaspooryorik 🙏

@Daniel Mejia has left the channel

@atuttle at taffy,io the documentation section has Documentation is mostly available at docs.taffy.io, with the more detailed guides remaining in the GitHub wiki for now. The docs.taffy.io page has a link to download v3.3 -= despite 3.6 being the latest.

sorry about that. PR’s welcome to fix that. 😅

Brand new to taffy, installed it without issue and have it running, added a couple resources and these all work great from the Taffy dashboard at https://www.mydomain.com/api/ When I try calling them from code via cfhttp, i.e. url="https://www.mydomain.com/api/resourceName" I get a Connection Failure. "Connect Exception: Connect to www.mydomain.com:443 [www.mydomain.com/127.0.0.1] failed: Connection refused: no further information" It seems to me like its a port/permission issue but was wondering if anyone had any more info to point me in the right direction? I want to be able to provide my host with more info before I have them check it out. Thanks!

sounds like you’re missing your SSL certificate. try http instead of https, see if that works.

Thanks Adam, looks like that was it - removed the https and then monkeyed with the end point and its working now. I have the SSL through Cloudflare so I'll need to see how that is currently set. One question, I had to change it to https://www.mydomain.com/api/index.cfm/resourceName to get it to run, I do recall seeing that in the docs. Is there a way to get these calls to run without the index.cfm in the endpoint url?

requires URL rewriting https://github.com/atuttle/Taffy/wiki/URL-Rewrite-Rule-Examples

Thanks again Adam, really love Taffy so far!

👍

@atuttle Is Taffy not in active development at this point? I noticed that the latest version 3.6 was released 2.5 years ago!

what changes are needed?

I have a to-do list item to implement a couple of changes proposed by @tomchiverton for lucee 6 compatibility, but otherwise it’s just been stable.

My apps still use it in production, as a critical path component to collecting hundreds of thousands of dollars per year (per quarter, by now, maybe?) in e-commerce transactions.

I saw that lucee 6 compat issue and would welcome it as we are transitioning to Lucee from ACF in the coming months and would love to be on Lucee 6.

Our biggest issue right now is that if you have a required argument on a request function, then if the argument is not passed in we get an exception thrown. It would be nice for taffy to just trap that exception and return a 417 validation error response. Is there a way to do this currently?

interesting thought. I’ve known about that for a long time but never thought about handling it that way

personally I just mark everything as optional (as far as CF knows) and then do validations in the implementation (param with default, if value is default, then return an error)

would certainly welcome a PR that adds it 😄

that is what we have been doing but then the arguments are showing up in the taffy dashboard as optional and not required.

yep

Perhaps I will fork Taffy and see what I can do to improve these areas and if I am successful I will create a PR back to your repo.

cool, let us know how it goes 🙂

So, it appears the clock is ticking on the taffy.io domain: https://every.to/p/the-disappearance-of-an-internet-domain (tldr: the TLD may cease to exist in the next 3-5 years for complex geopolitical reasons, but we don’t know for sure yet) Any suggestions for where it should move, if forced? I have my doubts it will happen — mostly the stuff from the last section of the article, under the heading “the endurance of physical history” rings true to me…

@jeremyhalliwell has left the channel

set the channel description: Discussion and help for http://taffy.io ~The premier REST framework for CFML ~ DOCS: http://docs.taffy.io

Hi all. Forgive me please, as I suspect that the answer to my question is likely rather simple / obvious, but alas, it has thus far eluded me. I want to disable the Taffy dashboard in production as our users don't need access to it, and because I can do so it just seems like something I'd want to hide. But... I do, from time to time, need to reload the API cache if / when changes are made to those cfc's. One way to do this is for me to: A. change application.cfc to enable the dashboard B. restart CF C. go to the dashboard and click the button to reload the API cache D. change application.cfc to once again disable the dashboard E. restart CF But obviously this isn't terribly "elegant" and 2 CF restarts in production is a little "heavy handed". I've read the documentation on the framework's "reloadKey" and "reloadPassword" options and I suspect that this is exactly what I need to use instead of enabling the dashboard, but... I just don't know how to use those parameters to make the call to re-initialize? Many thanks in advance for your help!

Hey y’all. Figured I’d drop in to say that I recently released Taffy 3.7.0 that fixed a compatibility issue with Lucee 6. Thanks to @tomchiverton for the report!

FYI: Upgrading to ColdFusion 2025 breaks Taffy API Error message: Attribute validation error for tag CFHEADER. It does not allow the attribute(s) STATUSTEXT. The valid attribute(s) are CHARSET,NAME,STATUSCODE,VALUE. ColdFusion 2025 has removed the statustext attribute of cfheader as noted here: https://www.petefreitag.com/blog/coldfusion-2025-breaking/#:~:text=Removal%20of%20the%20statustext%20attribute%20of%20cfheader&amp;text=You'll%20now%20get%20this,from%20customizing%20the%20status%20text. I fixed my Taffy API by removing the attribute from all <cfheader> tags using it.