This is a question for you to answer. ColdBox supports the mode of being in debug mode or not. It does so, by placing a cookie on your browser so you can see the debugging panel only with that cookie set. The question is, how long should that cookie live? What should the expiration time be? Any suggestions?
Blog
Recent Entries
12 Days of BoxLang - Day 4: TestBox
Today we’re celebrating one of the most exciting new additions to the BoxLang ecosystem:
the TestBox BoxLang CLI Runner — a fast, native way to run your TestBox tests directly through the BoxLang Runtime. ⚡
No server required. No CommandBox needed. Just pure, ultra-fast BoxLang-powered testing from the command lineon Windows, Mac, and Linux.
If you’re building modern applications with BoxLang — web apps, CLIs, serverless functions, Android apps, or OS-level utilities — this new feature gives you a unified, flexible testing workflow you can run anywhere.
Victor Campos
Victor Campos
December
13,
2025
12 days of BoxLang - Day 3: SocketBox!
As BoxLang continues evolving into a modern, high-performance, JVM-based runtime, real-time communication becomes essential for the applications we all want to build: dashboards, collaboration tools, notifications, live feeds, multiplayer features, and more.
That’s where SocketBox steps in — the WebSocket upgrade listener built to work seamlessly with CommandBox and the BoxLang MiniServer. ⚡
Today, for Day 3, we’re highlighting how SocketBox supercharges BoxLang development by giving you fast, flexible, and framework-agnostic WebSocket capabilities.
Maria Jose Herrera
Maria Jose Herrera
December
12,
2025
12 Days of BoxLang - Day 2: CommandBox
BoxLang + CommandBox: The Enterprise Engine Behind Your Deployments
For Day 2 of our 12 Days of Christmas series, we’re diving into one of the most powerful parts of the BoxLang ecosystem: CommandBox the defacto enterprise servlet deployment platform for BoxLang.
If BoxLang is the language powering your applications, CommandBox is the engine room behind it all. ⚙️
Victor Campos
Victor Campos
December
11,
2025
Add Your Comment
(4)
Feb 23, 2007 03:50:04 UTC
by Sana
Hi Luis, I think 30 minutes, as sessions default expiry is 30 minutes, so this cookie should be 30 minutes expiry time.
Feb 23, 2007 07:29:14 UTC
by Dan Wilson
Luis, Perhaps it could be left up to the user to clear the cookie when they have finished the debugging? A link or a special URL perhaps to clear the cookie? Dan
Feb 23, 2007 10:00:43 UTC
by reuben
I agree with Sana that the time out for a cookie should be defaulted to the session timeout. If you are working constantly on the site, the debug will last beyond 30 minutes. The big issue is that if you stop work and come back to the site, you don't always want debug still enabled. I think having it auto expire is a good thing.
Feb 23, 2007 10:24:47 UTC
by Luis Majano
Dan, You can clear the cookie by just setting debugmode=false once you are done. But we all know that sometimes we are lazy and basically forget, like 90 year old brians!! So an automatic timeout, would allow security and also peace of mind. I think 30 minutes is reasonable. Any more suggestions.